Skip to content

Cancel superseded CI runs with a concurrency group - #32

Open
Nomadcxx wants to merge 1 commit into
masterfrom
fix/ci-concurrency
Open

Nomadcxx wants to merge 1 commit into
masterfrom
fix/ci-concurrency

Conversation

@Nomadcxx

Copy link
Copy Markdown
Owner

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 concurrency group keyed on workflow + ref:

  • workflow files that run on branch/PR pushes: 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

  • Each modified file parses as YAML and the parsed concurrency.cancel-in-progress value was read back to confirm it is true for CI-style workflows and false for the release workflow.
  • git diff --stat shows insert-only changes.

@Nomadcxx
Nomadcxx force-pushed the fix/ci-concurrency branch from 611f4ac to db11376 Compare October 1, 2026 10:57

This branch has not been deployed

No deployments
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