-
-
Notifications
You must be signed in to change notification settings - Fork 844
Linting of commands #701
Copy link
Copy link
Closed
Labels
good first issueIssues that are good for first-time contributors to pick up.Issues that are good for first-time contributors to pick up.help wantedIssues that could benefit from members of the community contributing their expertise or experience.Issues that could benefit from members of the community contributing their expertise or experience.
Metadata
Metadata
Assignees
Labels
good first issueIssues that are good for first-time contributors to pick up.Issues that are good for first-time contributors to pick up.help wantedIssues that could benefit from members of the community contributing their expertise or experience.Issues that could benefit from members of the community contributing their expertise or experience.
Type
Fields
Give feedbackNo fields configured for feature.
So this is not fully fleshed out in my head yet.
The gist is as such: my team currently uses makefiles + shell scripts to do things. this is obviously messy and awful.
I've done a few PoCs to migrate those things into taskfile and it's a beautiful world.
but here's the rub: we use shellcheck in all of our CI/vim/local machines/etc to verify shell scripts for various code smells.
I'd love to figure out a way to do this in taskfile, but I haven't used this tool enough yet to figure out how to do it.
I can think of a few hacky ways to do it. for example:
task --shell -t mytaskfile.yaml mytaskand it dumps that task as a mini-shell script. I can then pipe that to shellcheck.or even better, build shellcheck into task:
task --lint -t mytaskfile.yaml mytaskand it would run each command through shellcheck.the goal isn't to verify anything or do any complex stuff. the goal is to catch weird little typos or bad commands or other basic tripwire features.