-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add new GH shellcheck action #305
base: main
Are you sure you want to change the base?
Conversation
/cc @alknopfler |
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 for making this first PR
Triggering the test-ci manually, we'll merge the PR once the test has passed. |
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.
Checks triggered.
I have updated the branch just to make sure that all the latest changes pass the checks too. /lgtm |
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.
@leo8a sorry for the delay, but the pipe was not in shape for doing the testing.
We realized that with this PR in place, it breaks apparently the copy of some files and hence, the installation fails:
This works fine on main
branch.
I would suggest to split this into different PR's:
- One for the GHA for the checks
- One PR for each of the file changes, in that way, we run the pipe to see if it gets affected on that specific file and change without having to debug or rework on it as a whole
What do you think?
Thanks @leo8a! Rebasing the PR branch and testing again. |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
This GH action checks (in every commit to main) the shell scripts. Will only flag `severity: error` level problems as failures. Feel free to add `warnings` as error too if you need so.
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 for me, let's try to get the other stuff in and merge this
This PR adds a GH action that checks errors in shell scripts for every commit to main. As a complement, fixes to pass the shellcheck linter can be found in #397, #398, #399, #400, and #401.
Signed-off-by: Leo Ochoa [email protected]