chore: Added concurrency group to the pr workflow to automatically cancel previous low priority workflows - #2212
Merged
Conversation
…ncel previous workflow
RabiyaF
added
Scope: CI
rprospero
approved these changes
Jul 25, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I am adding concurrency groups to the pr workflow to automatically cancel the previous workflows if commits are pushed in quick succession. This is because the runtime of the PR checks is over 3.5 hours (see link) and we should not be running them unnecessarily.
I recently saw that metrics of actions are now available on GitHub. As the pr.yml is the action that has the highest runtime across the runners, hopefully this change will make development more sustainable. And we can track the reduction in total jobs runs and total minutes next month.