GitHub Action Concurrency Failing To Cancel Irrelevant Runs#247
Merged
dchansen06 merged 1 commit intomainfrom Feb 20, 2026
Merged
GitHub Action Concurrency Failing To Cancel Irrelevant Runs#247dchansen06 merged 1 commit intomainfrom
dchansen06 merged 1 commit intomainfrom
Conversation
Signed-off-by: Daniel Hansen <dchansen06@gmail.com>
1d212d8 to
99a5712
Compare
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
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.
Fix GitHub Action Group Concurrency
Problem and Scope
Rapidly pushing individual commits queues up massive amounts of runs that are not cancelled since concurrency groups blocking this are grouped with run IDs
Description
No longer group against run ids
Gotchas and Limitations
May take a little time to cancel
Testing
Testing Details
Re-pushed off of 1d212d8 with 99a5712 and validated that it cancelled
Larger Impact
Pushing every commit no longer triggers up the same workload as it did before
Additional Context and Ticket
Resolves #246