Add concurrency in CI #9855
Merged
Add concurrency in CI #9855
Conversation
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
browniebroke
approved these changes
Dec 23, 2025
Member
browniebroke
left a comment
browniebroke
left a comment
There was a problem hiding this comment.
Nice! I usually use group: ${{ github.head_ref || github.run_id }} but I checked the docs and what you're proposing seems indeed better for our setup since we have multiple workflows 👍🏻
Contributor
Author
|
Thanks Bruno ! |
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.
With concurrency, if a previous run is still going, it will be stopped and only the latest run will finish.
This is especially helpful for immediate pushes. For example, if I push code and then immediately push a fix 10 seconds later, GitHub will stop the first (outdated) run and only spend resources on the latest one.