-
Notifications
You must be signed in to change notification settings - Fork 32
linting: add shellcheck for shell script lint #756
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
base: main
Are you sure you want to change the base?
Conversation
3b2e198 to
ad1f9e0
Compare
e61a5c5 to
8635352
Compare
hanno-becker
left a comment
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.
Thank you @L-series, in general I think linting the shell scripts is a great idea -- esp. seeing that at least I'm not a shell expert.
However, it looks like some of the quoting has broken scripts/lint, at least the Lint Shell command. Can you have a look, both at the issue itself and why the CI did not catch it?
|
@hanno-becker Hello, please see my comment above regarding what the issue was with the I'm adding a variable which tracks the shells scripts which exist across the project and I pass that to both |
054002b to
67a36aa
Compare
c2209ca to
7482a42
Compare
f2f74f3 to
9dd0fa7
Compare
8c1b11e to
f17ce9f
Compare
9430670 to
397da23
Compare
Add linting for shell scripts in the scipts directory as well as any *.sh file accross the project using shellcheck. Signed-off-by: Andreas Hatziiliou <[email protected]>
Fix errors brought up by the linter. Signed-off-by: Andreas Hatziiliou <[email protected]>
Add linting for shell scripts in the scipts directory as well as any
*.sh file accross the project using shellcheck.