ci: one job for the repository's script checks #260
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/one-job-for-repo-checks"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ci: one job for the repository's script checks
Six workflows, nine jobs on every push (lockfiles, tests-in-ci, workflow-hygiene,
wai-section-refs, spec-refs, and no-vanity-metrics' four), each paying for a container
and a checkout to run a script that reads the tree for a few seconds. On 2026-10-14
they were about half of the 119 jobs waiting for the linux-arm64 runner, queued behind
the long standards-build legs; spec-refs held a place on the one x86_64 runner.
repo-checks.yml runs them all in one job on linux-arm64, one step a check, in the same
order with the same self-tests. Every step runs even after an earlier one fails
(
!cancelled()), so a red job names each failing check, and fails if any did. Thepublic-name check still runs only on the push to main, where its pattern list is
given. The two path filters (public text, WAI section references) are dropped: the
checks take seconds, and a filter that is wrong skips a check silently.
check-workflow-concurrency-selftest.sh takes the new file as its fixture (it removed
the concurrency block from workflow-hygiene.yml, now gone); CHARTER.md names the new
workflow. Locally: the concurrency self-test and check (24 workflows), the path-gate
self-test, tests-in-ci, spec refs and vanity metrics pass, and the workflow parses
(19 steps).
🤖 Generated with Claude Code