Idee: batch-configuration should be like a pluing for the project. User, who use teco/sdil conventions, shouldn't need to change anything on the plugin. And when the convention change, the plugin should update automatically.
move schedule.sh (and supporting files) into .batch subfolder in the actual projects
put the configurations into separate repositories
--> you can add "git_batch" to your project with git-submodule
Idee: batch-configuration should be like a pluing for the project. User, who use teco/sdil conventions, shouldn't need to change anything on the plugin. And when the convention change, the plugin should update automatically.
--> you can add "git_batch" to your project with git-submodule
so examples look like: