Repository navigation
Add an 'All checks' aggregate job to CI - #121
Merged
Merged
Conversation
GitHub only blocks a merge on status checks that branch protection names. This job needs every other job in the workflow and fails unless all of them succeeded, so branch protection can require just it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
hcaballero2
approved these changes
Oct 16, 2026
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
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.
Adds an
all-checksjob (named 'All checks') to the CI workflow. GitHub only blocks a merge on status checks that branch protection lists by name; this jobneeds:every other job in the workflow and fails unless all of them succeeded, giving branch protection one stable check to require. The pupmod fleet already has the same job in its PR Tests workflow.After merge
Require the new check, 'All checks', in branch protection. Requiring it before it exists would leave PRs waiting on a check that never reports.
Testing
actionlint 1.7.7: nothing reported for the added job. Pre-existing findings elsewhere in the file (unknown ubuntu-26.04 runner label in older actionlint, shellcheck SC2046 warnings) are untouched.
The job's
needs:list was verified against the workflow's job ids.🤖 Generated with Claude Code