Introduce github action linting in pre-commit #1065
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This checks github action files in pre-commit. To run this locally, make sure you have
shellcheck
installed.actionlint
found these kind of problems and this PR addresses them ($ actionlint -oneline
).$(...)
notation instead of legacy backticks `...`printf
format string. Useprintf '..%s..' "$foo"
-n
instead of! -z
{ cmd1; cmd2; } >> file
instead of individual redirects"github.event.comment.body"
is potentially untrusted. avoid using it directly in inline scripts. instead, pass it through an environment variable. see https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions for more details$
somewhere? - I have ignored that one because I think it was a false report. Wasn't it?Here's a detailed list of all the problems that actionlint found: