-
Notifications
You must be signed in to change notification settings - Fork 51
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
PROPOSAL: Add Codacy to check code quality #552
Comments
+1, I was thinking a shellcheck action but this should be fine to test. I can add it at an org level but would prefer to test it in one repo that isn't main first to get a feel for it. I don't mind just turning it on as a nonblocking check in bluefin for a while, lmk. |
For sure! I think this would be valuable in all repos. We most certainly don't need to turn it on in main first :) |
I've got this on in Bluefin and a few others and it seems fine. Any other feedback from approvers? |
Since we are considering splitting out our container files into smaller bash scripts (rather than doing inline bash), I think it would be helpful to have a code analysis tool to help with consistency and code quality: https://www.codacy.com/pricing
The open source plan is free and it can be added as a check in Github on a repo.
See JasonN3/build-container-installer#100 as an example.
The text was updated successfully, but these errors were encountered: