ci: supersede stale check runs - #12
Merged
Merged
Conversation
Checks now carry `concurrency` with cancel-in-progress so a newer push to the same ref kills the queued predecessor instead of stacking runs on the self-hosted pool. Release workflows get the same grouping with cancelling disabled — a publish must never be interrupted halfway.
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
1 participant
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.
A newer push to the same ref now cancels the in-flight check run instead of stacking another job on the shared runner pool. Release workflow keeps its own grouping with cancelling disabled.