Repository navigation
ci: add single 'gate' check context for the upcoming PR-gated main - #3
Merged
Merged
Conversation
The 'protect main' ruleset will require one stable check name instead of enumerating matrix cells: 'gate' aggregates the test+e2e matrices (plus CodeQL's 'analyze' is required separately). Docs (AGENTS.md, CONTRIBUTING.md) switch to the PR-based workflow: direct pushes to main rejected for everyone, release commits land via release PRs.
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.
Why
Switching this repo's development flow from direct pushes on
mainto a PR-based flow (strict: no bypass actors, admins included). A PR-gated ruleset needs required status checks — and requiring individual matrix cells (test (ubuntu-latest, 22.18), …) in the ruleset would silently drift every time the matrix changes.What
.github/workflows/ci.yml: newgatejob that aggregates thetest+e2ematrices into one stable check context (if: always(), fails unless both need-jobs succeed). The ruleset will requiregate+ CodeQL'sanalyze.After merge
Flip the
protect mainruleset: addpull_request(squash+merge allowed, 0 required approvals) +required_status_checks(gate,analyze; up-to-date branch required), and remove the admin bypass actor.