-
Notifications
You must be signed in to change notification settings - Fork 3
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
ci: Improve workflow files #111
Conversation
Because workflow_run is weird and doesn't trigger on branches other than the default one like 'main' or 'master'. In conclusion: This trigger is weirdly designed and pretty much useless.
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.
Did you have the chance to test it e.g. in a fork?
No, but I can try it. |
@@ -1,20 +1,16 @@ | |||
# ============= |
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.
I assume the plan is to upstream this back into templating?
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.
Yes. This is the ultimate goal. Depends how much we can re-use in the operator repos tho.
pull_request: | ||
merge_group: |
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.
Definitely still want to run this for merge groups too?
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.
If we check on every PR, we should not need it when merging as the code is tested and built beforehand. This ensures we don't push broken code into main.
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.
I think we can start with this and improve it gradually if any problems arise
Tracked by #98
This PR reworks and streamlines GitHub Action workflow files. It tries to reduce runs by selecting which workflows to run based on file paths. It also limits on which events these workflows get triggered.
We currently (and will never) allow direct pushes to
main
. That's why it is sufficient to only run onpull_request
for most of the workflows. Release workflows on the other hand get triggered by pushes (to main) with tags attached.EDIT: We might want to re-add the
merge_group
trigger for workflow files which currently only usepull_request
.actions-rs/clippy-check
togiraffate/clippy-action
Stackable Build Pipeline
into new workflows