Add CI concurrency group for some workflows #255
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Add CI concurrency group limiting to one build per branch, canceling any older runs.
Why
See discussion here. Goal is to reduce cost and limit CI resource usage. This change will make it so that CI runs are canceled when new commits are pushed, except on protected branches (ex.
main
)Note that the only workflow that is actually costing us money is
e2e
. Since this repo is public, all workflows that run on standard github runners (which is everything else) are free. So if for some reason we still want/like the runs for the other workflows to keep going when new commits are pushed, we could eliminate the changes there and just keep thee2e
workflow changes.