ci: a push cancels its branch's older run, checkout keeps no token (closes #216)

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
2026-10-02 06:07:53 +02:00
parent dba932c9e3
commit a67fd20e4f
2 changed files with 10 additions and 0 deletions
@@ -19,6 +19,8 @@ trial run of the finished image: https://git.eeqj.de/sneak/dnswatcher/issues/149

 # Completed Steps

+- 2026-10-02: a push to a branch cancels that branch's older CI run, and the
+  checkout leaves no token in `.git/config` (closes #216).
 - 2026-10-02: watcher tests send far fewer queries and a live attempt may take
  18s; nameserver addresses are asked only for A, AAAA, CNAME (closes #214).
 - 2026-10-02: the resolver tries root servers, and every other server list it