Hi @jnormile @AidanNeeson ! This is a draft of the changes that allow you to take in a list of values for Google Sheets configuration as well as GitHub configuration.
As you can see in my example command, you have to include the flag before you provide each input. So here is how that would look like:

If you want to use a combination of directories and files and Sheets Config, you have to include the -sc flag before each argument.
Correct Command:

$ sheetshuttle run -sc file1.yaml -sc file2.yaml -sc dir1/ -sc dir2/file3.yaml

You cannot put the flag once.

Incorrect Command:

$ sheetshuttle run -sc file1.yaml file2.yaml dir1/ dir2/file3.yaml

Another thing to note is that there is no validation being done on the input whatsoever. The only modification is to cast the string into a Path object. So with that in mind, the list of values is passed on to the plugin with little modifications and no validations.

Keep in mind that depending on how you want to use the values in that list, you should:

• Check if the item is a file or directory
• Check if the item exists on the file system
• Other checks might be needed too, but they can be done easily since each item is a Path object.

Can I get you feedback on whether this approach in taking in the CLI values is acceptable or not? I'd like to know what you think before I continue with the remaining changes. Thanks!

@noorbuchi , this implementation seems like it would work for our project to me! @AidanNeeson , do you see any problems I might be missing?

The most recent changes allow the SheetCollector infrastructure to take in a list of pathlib.Path objects to use as yaml sources of configuration. Several checks are made after SheetCollector.collect_files() is called to make sure that:

• Every path in the list exists
• Every path in the list points to a file (not to a directory)
• Every path in the list points to a yaml file (aka. with a .yaml or .yml suffix)

I have to do something similar for the GitHub interactions. I'm hoping to get started on that soon as well. Please let me know what you think of the current implementation to far.
If you think this PR looks good, we can go ahead and merge it as it currently stands. Then adding this feature for the GitHub side of things can be done later if it's not currently a priority. Let me know what you prefer.

@noorbuchi Our particular implementation doesn't require any of the GitHub interactivity--it's all purely on the Google Sheets side. So no rush at all on implementing the GitHub side of things.