-
Notifications
You must be signed in to change notification settings - Fork 152
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 Checkton workflow #1183
Add Checkton workflow #1183
Conversation
FYI, I've opened a proposal for Checkton to move to the tektoncd org: tektoncd/community#1156 But even before that's resolved, let's start using it already? |
The output looks like this: We could also upload the generated SARIF file to make GitHub show the warnings inline. But currently, there is an annoying bug (or feature?) where the warnings never go away even if you fix them - https://github.com/orgs/community/discussions/132787. |
/retest |
/retest |
Tests timed out while waiting for the enterprise-contract pipeline to pass Tekton was very lazy today, just refusing to schedule any steps. Even the Tekton built-in ones
|
/retest |
It doesn't need to run the Konflux pipeline when changes are made to |
Checkton is a GitHub action that runs ShellCheck on scripts embedded in YAML files (https://github.com/chmeliik/checkton) Signed-off-by: Adam Cmiel <[email protected]>
If you don't want to push to a PR just to re-run the linter, you can use this script. Won't work on ARM Macs, sorry! Signed-off-by: Adam Cmiel <[email protected]>
Rebased on main
True, but we can't merge without it. I'll see if we can make it not run when those are the only two dirs that changed. There was an attempt to do this by enumerating all the directories for which we do want to run the pipeline (#524), but that seemed very fragile. |
And IMO we do need to run the pipeline on changes to |
Yes. 👍 |
Checkton is a GitHub action that runs ShellCheck on scripts embedded in YAML files (https://github.com/chmeliik/checkton)