Skip to content

ci: cancel a pull request's superseded check runs - #47

Merged
WilliamSmithEdward merged 1 commit into
mainfrom
ci/concurrency
Nov 18, 2026
Merged

WilliamSmithEdward merged 1 commit into
mainfrom
ci/concurrency

Conversation

@WilliamSmithEdward

Copy link
Copy Markdown
Owner

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.

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.
@WilliamSmithEdward
WilliamSmithEdward merged commit 5472c79 into main Nov 18, 2026
21 checks passed
@WilliamSmithEdward
WilliamSmithEdward deleted the ci/concurrency branch November 18, 2026 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant