[FEATURE] More versatile inclusion of multiple job files

[drws]

Is your feature request related to a problem? Please describe.

Multiple job files can only be used with --jobs in CLI while there is no corresponding config.yaml directive.

Describe the solution you'd like.

--jobs (and possibly --hooks) should also be supported as a config.yaml directive.

Another, somewhat more thorough, but a minimalistic solution, is to move jobs.yaml into a (sub)directory - from which all files are (recursively) included by default. --jobs (and --hooks) could be repurposed for specifying the directories (paths). Smart file specification could be removed entirely.

[mborsetti]

@drws Thank you for your contribution(s)!

I am a bit confused as --jobs accepts a glob and can be repeated as many times as you want.

I cannot check at the moment, but a --jobs ./these jobs/* should work!

[drws]

Initial issue description had flaws so I rewrote it later. Perhaps you read the first version of the issue. The main problem is that one cannot put jobs: jobs/*.yaml directive into config.yaml.

The above directive matches multiple files, but in a single directory level. Having separate directories for jobs and hooks extends the current logic, but it could also replace it (for keeping it simple). So it's a side discussion what to do with dedicated directories. Just to be clear, the $XDG_CONFIG_HOME/webchanges directory would contain (by default):

./config.yaml
./jobs/jobs.yaml
./hooks/

Webchanges would simply read the whole ./jobs tree for job specifications and the whole ./hooks tree for hooks. Both paths would be configurable with --jobs and --hooks. If the provided path represented a file, it would be included as is now, and if it represented a directory, webchanges would recursively search it. Globbing itself does not allow for directory-structure organization, recursion is needed for that.