Skip to content

docs: document the CI OK aggregate required check (toon-meta#279 proof) - #164

Merged
ALLiDoizCode merged 2 commits into
mainfrom
epic270/279-aggregate-check-docs-proof
Aug 8, 2026
Merged

docs: document the CI OK aggregate required check (toon-meta#279 proof)#164
ALLiDoizCode merged 2 commits into
mainfrom
epic270/279-aggregate-check-docs-proof

Conversation

@ALLiDoizCode

Copy link
Copy Markdown

Documents the CI OK aggregate required check added in #154, and is itself the acceptance proof for it.

This PR touches exactly one file — CONTRIBUTING.md — which matches none of the Detect Changed Paths filters (rust, desktop, desktop-rust, web, mobile). So every paths-filtered job in ci.yml skips.

That is precisely the case toon-meta#279 exists to close. Before the aggregate, such a PR produced an effectively empty check set: nothing verified it, and "no failing checks" was trivially satisfied. Now:

  • Detect Changed Paths and Dead Token Reference Guard run unconditionally and must succeed.
  • Every filtered job reports skipped, and CI OK re-evaluates each job's own if: expression against the detect outputs to confirm the skip was legitimate.
  • CI OK reports a definitive pass — not an absent check, not a neutral one.

Had any job been skipped while its filter said it should have run, CI OK would fail with Job '<id>' was expected to run ... but was skipped.

Part of toon-protocol/toon-meta#270
Part of toon-protocol/toon-meta#279

🤖 Generated with Claude Code

ALLiDoizCode and others added 2 commits August 6, 2026 12:06
Records how buzz's single required status check works: it recomputes each
job's trigger condition from the Detect Changed Paths outputs, so a skipped
job only passes when its paths genuinely were not touched, and a docs-only
PR still gets a definitive verdict rather than an empty check set.

This PR is itself the proof case for that behaviour — it touches no
paths-filtered path, so every filtered job skips and CI OK must still
report a real pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The previous two attempts had 'Detect Changed Paths' (timeout-minutes: 2)
sit ~19 minutes without starting a step before being cancelled — the jobs
never got a runner. Retriggering on a fresh SHA to get a clean verdict.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant