-
Notifications
You must be signed in to change notification settings - Fork 17
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
For Reference and cherry-picking: Shellcheck fixes #328
base: main
Are you sure you want to change the base?
Conversation
f20efeb
to
14b90bd
Compare
Is this PR still needed? |
In my opinion it is too much to fix all ShellCheck issues in a single PR. It's almost impossible to review. I just added another PR (#356) to introduce ShellCheck with exceptions for files with issues. I would prefer to merge that one and split this PR into smaller chunks that could be reviewed easier and that remove the corresponding exceptions in the same PR. |
sounds good to me. In that way, we can get the packages, that are finished already faster into the main branch. |
8dd3056
to
ce886b1
Compare
semver.sh is not our own library. We shouldn't check it therfore. This precedes #315. Signed-off-by: Martin Hübner <[email protected]>
adjust dependencies, to include jshn too. Signed-off-by: Martin Hübner <[email protected]>
noteworthy: removed backtick-notation for subshell calls. Signed-off-by: Martin Hübner <[email protected]>
Signed-off-by: Martin Hübner <[email protected]>
Signed-off-by: Martin Hübner <[email protected]>
Signed-off-by: Martin Hübner <[email protected]>
Signed-off-by: Martin Hübner <[email protected]>
ce886b1
to
d79576e
Compare
Just for letting you know whats going on here: For the commits, that are still valid, I cherry-pick them into other PRs one by one, adjusting them to the current state too. |
Afterwards I drop them here. |
Fixes stuff for #315