docs(gate): document the merge-time rust-gate bypass - #807
Merged
Merged
Conversation
…est-mode ruleset actor)
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.
Documents the full bypass story for the new Rust test gates:
git push --no-verifyorFRESHELL_PREPUSH=0(already documented).rust-gate: the owner account is now apull_request-mode bypass actor on the 'Protect Main - No Direct Push' ruleset (ruleset 14348583, configured via the API alongside the required-check patch from feat(gate): targeted cargo test lane at push time + required rust-gate CI check #803). Merging with a red or missingrust-gateis justgh pr merge <n> --mergefrom that account; GitHub records it as a ruleset bypass with an audit entry. It does not unlock direct pushes to main — that rule stays fully enforced.Context: the required
rust-gatecheck went live with #803 and has since passed on real traffic (PR #805 ranrust-tests+rust-gate, both green — main is Rust-green again after the sixpack fixed the 11 #795 failures). This PR adds the explicit escape hatch so landing on a red base remains a one-command, audited action rather than a ruleset edit.