ci: add all-checks aggregator job for branch-protection rulesets - #2
Merged
Conversation
Mirrors the pattern from Thurbeen/thurbox. A single `All Checks` job whose status rolls up `markdown-lint`, `schema-validate`, `link-check`, and `conventional-commits` means the repository ruleset references one stable check name; adding or removing individual CI jobs no longer forces a ruleset edit. The `if: always()` plus `contains(needs.*.result, 'failure'|'cancelled')` pattern ensures the aggregator fails fast on any sub-job failure (or cancellation) and passes only when every dependency succeeded.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
All Checksaggregator job toci.ymlthat depends on the four existing CI jobs (markdown-lint,schema-validate,link-check,conventional-commits).if: always()+contains(needs.*.result, 'failure'|'cancelled')pattern fails fast on any sub-job failure or cancellation; passes only when every dependency succeeded.Why
Mirrors the pattern from
Thurbeen/thurbox: a single stable check name for repository rulesets to reference. Adding or removing individual CI jobs no longer forces a ruleset edit — just update this job'sneeds:.What's next
A follow-up step (no PR — server-side config via
gh api) creates aprotect-main-branchruleset on this repo requiring this newAll Checksstatus, plus deletion/non-fast-forward protection and required PRs with rebase merges.Test plan
All Checksstatus reports green at the end of the pipeline.