Each push to a branch now cancels that branch's older run of the check workflow, queued or running, and the checkout step no longer leaves the token in .git/config (script/cibuild does not need it).
Why: every push queues a run on the runner the whole fleet shares, and a branch pushed again (a rebase, a rework) left its older run queued for a head nobody needs.
What the diff does not show:
A run joins a group only when the workflow file at its own head has the concurrency block. Runs queued before this lands, and pushes of branches not yet rebased onto a next that has it, are never cancelled.
The group is the workflow name plus the branch, so a push to another branch never cancels a run on next or main. A push to next does cancel the older next run, as the issue asks for every branch.
Disclosure:
Unverified: no run of this branch has executed yet (the runner is busy), so the checkout without a stored token has not been seen in a run.
Each push to a branch now cancels that branch's older run of the `check` workflow, queued or running, and the checkout step no longer leaves the token in `.git/config` (`script/cibuild` does not need it).
Why: every push queues a run on the runner the whole fleet shares, and a branch pushed again (a rebase, a rework) left its older run queued for a head nobody needs.
What the diff does not show:
- A run joins a group only when the workflow file at its own head has the `concurrency` block. Runs queued before this lands, and pushes of branches not yet rebased onto a `next` that has it, are never cancelled.
- The group is the workflow name plus the branch, so a push to another branch never cancels a run on `next` or `main`. A push to `next` does cancel the older `next` run, as the issue asks for every branch.
Disclosure:
- Unverified: no run of this branch has executed yet (the runner is busy), so the checkout without a stored token has not been seen in a run.
Closes https://git.eeqj.de/sneak/dnswatcher/issues/216
Model: opus-5-5
Every push queues a run on the shared runner, and a branch pushed again
left its older run queued for a head nobody needed. The workflow now puts
each branch's runs in one concurrency group with cancel-in-progress, so a
new push cancels that branch's older run, queued or running. The group is
keyed on the branch, so pushes to other branches never cancel runs on
`next` or `main`; a push to `next` itself does cancel the older `next` run.
The checkout step no longer writes the token into `.git/config`;
`script/cibuild` does not need it.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Each push to a branch now cancels that branch's older run of the
checkworkflow, queued or running, and the checkout step no longer leaves the token in.git/config(script/cibuilddoes not need it).Why: every push queues a run on the runner the whole fleet shares, and a branch pushed again (a rebase, a rework) left its older run queued for a head nobody needs.
What the diff does not show:
concurrencyblock. Runs queued before this lands, and pushes of branches not yet rebased onto anextthat has it, are never cancelled.nextormain. A push tonextdoes cancel the oldernextrun, as the issue asks for every branch.Disclosure:
Closes #216
Model: opus-5-5
Review passed on
d1a687d.Model: opus-5-5
d1a687de26to864fa34bed