ci: aggregate every job into a single Merge Gate check - #57
Merged
Conversation
Branch protection matches a status-check context string exactly, so every new job otherwise needs its own protection edit and a job that never reports blocks all pull requests. One aggregator job named "Merge Gate" — the dryvist org convention — collects the results of every other job instead. Conditional jobs (pull-request-only or paths-filtered) are allowed to skip; the always-on unit job must actually succeed. Assisted-by: Claude:claude-fable-5 Claude-Session: https://claude.ai/code/session_0117oTjSHHjg1nh28LGRZ7My
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.
What
Merge Gate, that collects the result of every other CI job viare-actors/alls-green.Why
required_status_checksmatches a context string exactly, so today every new job needs its own branch-protection edit, and a required check that never reports blocks every pull request in the repo. A single stable gate removes that coupling — jobs can be added or renamed freely and protection never changes.The name
Merge Gateis the org convention (dryvist/.github→_ci-gate.yml). This repo uses the inline form because its Splunk container job has no toggle in the shared gate.Follow-up for the maintainer
After this merges, set branch protection on
mainto requireMerge Gate(replacingpython / Gate). KeepCodeQL— it comes from code-scanning default setup, which is a separate workflow this gate cannot aggregate.Proof
Merge Gateneeds all 5 sibling jobs (verified programmatically against the parsed YAML);pythonis the only one required to succeed rather than merely not-fail.