Commit message · litbot-9000ci: skip matrix jobs at the job level outside their tier
The required matrix legs of unit-test, basic-integration-test,
cross-compile and dep-pin were kept instantiated in the pr and held
tiers and only skipped their steps, because a job-level condition is
evaluated before the matrix expands and a skipped matrix job never
reports the per-leg check names that the ruleset required. Every PR
push therefore occupied 13 runners for legs that did nothing, and a
held run 19.
Once CI result is the only required status check, those legs can be
skipped at the job level. The unit-test matrix is split into unit-test
(unit-cover and unit-module, all tiers) and unit-test-merge (the rest,
merge and nightly tiers) under the same name, so the check names stay
the same. basic-integration-test only runs in the merge and nightly
tiers, and cross-compile, unit-test and dep-pin skip at the job level
for documentation-only changes, drafts (cross-compile only) and held
runs.
CI result now lists unit-test-merge in its needs and tier lists, and
requires static-checks and lint in the pr tier. On pull requests it
lets the documentation-only and draft skips pass explicitly instead of
relying on step-level no-ops, and it requires check-commits on every
pull request run, so that the Check commits status check can be
dropped from the ruleset as well.
This must only merge after the ruleset requires CI result alone,
otherwise PRs wait forever for per-leg checks that are no longer
reported.
100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queueddocumentation-only discount