-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lint shell scripts #91
Conversation
12421e2
to
2173beb
Compare
Was using tabs instead of spaces intentional? I use shellcheck in my ci (and locally) In the ci use format=diff and locally let it use the gcc format for output. https://github.com/SickChill/sickchill/blob/master/.github/workflows/pythonpackage.yml#L60 |
No it wasn't 😅 Seems that's the default |
2daf449
to
4d67864
Compare
Want to take another look at this @miigotu? 🙂 In particular, do you agree with the |
I'll go over the whole thing when I get home, but absolutely It would also make the changes in this PR more apparent. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great now. You later can make an action that automatically fixes shell scripts in PRs if someone doesn't have an IDE that supports editorconfig and also don't have pre-commit installed.
👍
Adds
shfmt
andshellcheck
to our linter setup. Only the${INSTALLATION_ARGUMENTS}
call inmain.sh:20
looks like it cannot be formatted according to shellcheck, so I've added ignore statements for those. This mainly re-formats the old script files.Also sets
set -eo pipefail
to make the action error properly. The "command poetry does not exist" output for when the installation failed is not very user friendly.