Adrià FranchandClaude bca62ea696 ci: let a push to main cancel the build of the previous one ...

Push builds of main ran one after another, so a merge waited for the
builds of every earlier merge before main got a result for its tree; a
fix of a red main sat behind a build of the tree it fixes. The newest
push now cancels the build in progress, like pull request and dispatched
builds already do. The merge queue's baselines already skip cancelled
main builds and use the nearest completed ones.

Co-Authored-By: Claude <noreply@anthropic.com>

2026-10-16 19:14:07 +02:00

..

DISCUSSION_TEMPLATE

docs: point the bring-up form to the blocker map

2026-10-12 21:11:37 +02:00

ISSUE_TEMPLATE

docs: add a performance report issue form and ask for summary lines

2026-10-12 18:23:52 +02:00

workflows

ci: let a push to main cancel the build of the previous one

2026-10-16 19:14:07 +02:00

actionlint.yaml

ci(linux): move builds to self-hosted runner with persistent caches

2026-10-14 15:31:22 +03:00

dependabot.yml

ci: keep GitHub Actions up to date with Dependabot

2026-09-29 10:12:03 +02:00

labeler.yml

ci: label pull requests by area

2026-09-28 15:50:48 +02:00

pull_request_template.md

docs(contributing): ask GPU changes to name the GPUs their tests ran on

2026-10-13 07:45:50 +02:00