ci: concurrency-cancel on same-branch pushes #43

Closed

goldstein wants to merge 1 commit from fix/ci-concurrency into main

Author	SHA1	Message	Date
Dirk Riemann	f17ca00bbb	ci: add concurrency-cancel on push to the same PR / branch Some checks failed tests / test (pull_request) Successful in 1m9s Details tests / test (push) Failing after 11m18s Details 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>	2026-04-18 19:51:24 +02:00

Author

SHA1

Message

Date

Dirk Riemann

f17ca00bbb

ci: add concurrency-cancel on push to the same PR / branch

tests / test (pull_request) Successful in 1m9s

Details

tests / test (push) Failing after 11m18s

Details

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>

2026-04-18 19:51:24 +02:00