ci: concurrency-cancel on same-branch pushes #43
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/ci-concurrency"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Runner capacity=1 serialises CI across all repos. Without cancel-in-progress, quick follow-up pushes queue behind stale runs and delay useful feedback. This block drops obsolete runs as soon as new commits land on the same ref.
Forgejo runner runs with `capacity: 1` (one job at a time across every repo it serves — mammon, infoxtractor, etc.). Without a concurrency block, rapid-fire pushes to the same PR branch all queue behind any task already running, burning the runner for 30+ min on stale commits. `concurrency: { group: ci-$ref, cancel-in-progress: true }` tells Forgejo to cancel any still-queued or still-running CI on this ref as soon as a newer commit shows up. Applies to both push and pull_request events. (Previous PR bodies noted a "trigger bug" where I saw no CI response on a push — that was actually just the capacity=1 queue with no visible signal; the CI always fired, just minutes later. Runner capacity bump lives in infrastructure, not this repo.) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>Pull request closed