fix: add concurrency group for ci workflow #1816
Merged
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
rahulait
requested review from
ArangoGutierrez,
cdesiniotis,
elezar,
shivamerla and
tariq1890
as code owners
rahulait
force-pushed
the
add-concurrency-group
branch
from
81e9b46 to
5864ce3
Compare
Contributor
Author
|
/ok to test 5864ce3 |
rajathagasthya
approved these changes
Oct 24, 2025
Signed-off-by: Rahul Sharma <[email protected]>
rahulait
force-pushed
the
add-concurrency-group
branch
from
5864ce3 to
a5326d7
Compare
Contributor
Author
|
/ok to test a5326d7 |
tariq1890
approved these changes
Oct 28, 2025
cdesiniotis
approved these changes
Oct 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Adding concurrency group helps in preventing multiple concurrent workflow runs for the same PR. When a new commit is added to the PR, old workflow runs still running for the PR should get cancelled as they are no longer relevant and it should start again. This PR adds concurrency group with
cancel-in-progressset which makes sure stale workflow runs gets cancelled and we don't waste GHA cycles for runs/steps which don't matter as the code has been updated.