Move tasks to config file

[MichaelCurrin]

This means no command line work for symlinks.

It also prevents scripts from being added to the project which can be good. They then live in bin or other user directory that may or may not be executed from anywhere.

The config could even include shell commands in one item for arguments but then it lives in this project.

Benefit is text editor or even jekyll manager can be used to edit the file.

Note that syntax of file can be bad so gui helps.
And a broken symlink is the same on the old and new method.

Remember each task will be run separately. And maybe even may or may not have arguments. may be a full path or just name of bin script

[MichaelCurrin]

It can be text file, one command (path or bin script) with optional arguments per line.

No need to use use CSV or YAML (just a list). No need to use a webbrowser - just to VS Code locally to edit a text file.

If one needs to run each of the scripts, they can be copy and pasted to terminal or run with force run.

Add command or script to run alone, perhaps before each task is actually run too but that will just give a different error message. Purpose - to check the paths are valid, I could later add validation - is path valid or can script be found using which? Trim off any FOO=bar at the start though.

[MichaelCurrin]

Perhaps two configs - global user file if it exists otherwise repo file.
The test config would be inside the repo.

[MichaelCurrin]

The global directory could be created on make/pip install with empty text file. Only treat it is as a config if it is non-empty though?
Or combine two task lists.
What is the least surprising behavior?