Add concurrency groups for (relevant) workflows to cancel existing run when new one starts and group dependabot actions updates#950
Merged
Conversation
thehrh
changed the title
JanWeldert
approved these changes
Jun 10, 2026
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.
This is intended to save resources: I do not believe it is necessary for either of these workflows to complete when a new one has already begun (consider quick successive pushes to a PR or multiple PR's being merged in quick succession).
The syntax used here is taken from:
I haven't added concurrency control to the two release workflows because the above use case doesn't seem to apply to them.
The PR should also ensure that future actions updates by Dependabot end up in a single PR.