ignacionelson c05927c190 Let a newer push cancel the test run it supersedes ...

The linter has had this since it was written; the suite, which is the
expensive one, never got it. Two pushes landing together ran two full
suites to the end, and the earlier one was checking a subset of what the
later one checks.

Keyed on the ref, so main and a branch never cancel each other, and a
branch with an open pull request does not fight itself — push and
pull_request arrive under two different refs.

One consequence worth stating rather than discovering: on main an
intermediate commit can end up with no run of its own when two pushes
land close together. That is the right trade when what is being verified
is the state of the branch, but it is not free — a bisect or a release
audit that needs a particular commit's own green tick needs that commit
pushed on its own.

2026-08-27 01:50:09 -03:00

..

cla.yml

Skip the CLA job instead of starting a runner to skip a step

2026-08-27 01:48:58 -03:00

lint.yml

Stop spending CI time on checks that check nothing

2026-08-23 23:59:53 -03:00

tests.yml

Let a newer push cancel the test run it supersedes

2026-08-27 01:50:09 -03:00