Open noelmiller opened 7 months ago
+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.
+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 https://github.com/JasonN3/build-container-installer/pull/100 as an example.