Skip to content

CI: cancel a run that a newer push has superseded - #236

Merged
fredkiefer merged 1 commit into
gnustep:masterfrom
DTW-Thalion:ci/cancel-superseded-runs
Aug 11, 2026
Merged

CI: cancel a run that a newer push has superseded#236
fredkiefer merged 1 commit into
gnustep:masterfrom
DTW-Thalion:ci/cancel-superseded-runs

Conversation

@DTW-Thalion

Copy link
Copy Markdown
Contributor

main.yml runs on push and on pull_request and has no concurrency block, so a second push to a branch leaves the first run going. It answers a question about a tree nobody is waiting on, and nothing cancels it.

Over the last 90 days 49 of libs-back's 357 workflow runs were superseded while still running, 229 of 1736 wall-clock minutes. Taken from the Actions API over that window, counting a run as superseded when a later run for the same workflow and ref started before it finished.

The group is the workflow and the ref, so a run on one branch never cancels a run on another, and a push to master never cancels a pull request. A superseded run reports as cancelled rather than as a failure.

libs-base carries the same block, added in gnustep/libs-base#746.

main.yml runs on push and on pull_request with no concurrency block, so a second push to a branch leaves the first run going to answer a question about a tree nobody is waiting on.

Over the last 90 days 49 of libs-back 357 runs were superseded while still running, 229 of 1736 wall-clock minutes. The group is the workflow and the ref, so runs on different branches and on master are unaffected by one another.

libs-base carries the same block.
@fredkiefer
fredkiefer merged commit 37ec06e into gnustep:master Aug 11, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants