Repository navigation
ci: cancel a pull request's superseded check runs - #47
Merged
Merged
Conversation
A wave of pull requests and merges queued over a hundred runs that newer commits had already replaced, and every account shares one runner limit. CI, Security, Malware scan and Fuzz now share the standard concurrency block from repo-standards. A new push to a pull request cancels that pull request's older runs. A push to main waits for the run before it and never cancels one, and only the newest waiting run starts, so the tip of main is always checked. Scheduled, hand-started and Publish runs each get a group of their own. The gate still passes only when every job succeeded, so a cancelled run cannot satisfy the ruleset.
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.
A wave of pull requests and merges queued over a hundred runs that newer
commits had already replaced, and every account shares one runner limit.
CI, Security, Malware scan and Fuzz now share the standard concurrency
block from repo-standards. A new push to a pull request cancels that pull
request's older runs. A push to main waits for the run before it and never
cancels one, and only the newest waiting run starts, so the tip of main is
always checked. Scheduled, hand-started and Publish runs each get a group
of their own. The gate still passes only when every job succeeded, so a
cancelled run cannot satisfy the ruleset.