-
Notifications
You must be signed in to change notification settings - Fork 178
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
Apply all current ShellCheck suggestions and add lint-shell.sh
#1414
Conversation
Co-authored-by: David Parrish <daveparrish@tutanota.com>
@dmp1ce You were author of original PR, would be nice if you could take a look. |
@kristapsk Is there a reason we want to write the linters (or other scripts) in It's not a big deal, I'm just curious if there are specific reasons. |
No specific reason. I based old |
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.
LGTM. My only question is about commenting out old code that should probably be removed.
@PulpCattel @kristapsk Unless issues exist with the shell scripts they should stay as is because converting them to Python will likely cause a bug or two. Shellcheck does a good job of finding potential issues with shell scripts. |
Agree there is no much need to change what already works. But if we do convert to Python, likely we can just copy and modify little bit existing converted scripts from Bitcoin Core. That would lower possibility of introducing new bugs. Their current |
Based on #1175, but also covers
install.sh
changes since then, all other shell scripts and adds ShellCheck linter script. Not adding this to CI for now. I'm thinking we could split off all the linting to separate job, don't see a point in running them under all OS / Python version combinations.