Conversation
Nomadcxx
force-pushed
the
fix/ci-concurrency
branch
from
October 1, 2026 10:57
611f4ac to
db11376
Compare
This branch has not been deployed
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.
Problem
None of the workflows in this repo set
concurrency, so every push starts its own run: a burst of pushes to a branch or PR queues a full build per push instead of cancelling the superseded one. Each of those runs can fail independently and each failure produces a notification.Approach
Add a
concurrencygroup keyed on workflow + ref:cancel-in-progress: true— a new push cancels the in-flight run for that branch.release.yml:cancel-in-progress: false— a release must not be cancelled mid-flight, so superseded runs queue instead of killing the running one.No trigger, job, or step logic is changed. The diff is insert-only.
Verification
concurrency.cancel-in-progressvalue was read back to confirm it istruefor CI-style workflows andfalsefor the release workflow.git diff --statshows insert-only changes.