Repository navigation
ci: stop main pushes from cancelling each other - #52
Merged
Merged
Conversation
Back-to-back merges cancelled earlier main runs, and CI Success then reported the cancelled jobs as failures. PR runs still cancel superseded runs.
JacobCoffee
enabled auto-merge (squash)
October 10, 2026 22:44
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.
The recent red X's on
main(#48, #50, #47) weren't test failures. Those PRs merged within a few minutes of each other, and the sharedCI-refs/heads/mainconcurrency group withcancel-in-progress: truecancelled each earlier run ("Canceling since a higher priority waiting request for CI-refs/heads/main exists").CI Successruns withif: always()and failed because its needs were cancelled. Every job that ran to completion passed.PR runs keep one group per ref, so superseded PR runs are still cancelled. Pushes to
mainnow get one group per commit SHA, so every merge gets a complete run.Checked with zizmor (no findings) and actionlint.