docs: record the branch ruleset and close UPD-002 - #39
Merged
Conversation
The ruleset "main: require CI and protect history" is now active on the default branch: the Lint, typecheck, build, snapshot check is required, and main cannot be force-pushed or deleted. Repository admins are bypass actors on purpose. A required approval rule would leave a sole maintainer unable to merge their own work, so the status check is enforced and the approval requirement is left as a governance decision for when the reviewer roles in CONTRIBUTING.md section 5 are actually staffed. This pull request is also the end-to-end test of the gate: it is the first one that has to pass the required check before it can merge. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Records the ruleset now active on \main\ and marks UPD-002 done.
What is enforced
Repository admins are bypass actors deliberately. This repository is maintained by a very small group, and a required approval rule would leave a sole maintainer unable to merge their own work. The status check carries the value; the approval requirement is a governance decision for when the reviewer roles in CONTRIBUTING.md section 5 are actually staffed.
This PR is the test
It is the first pull request that must pass the required check before it can merge, so it verifies the whole chain end to end: workflow triggers, check name matches the ruleset context, and the merge is gated on it.
Documentation only - no \src/\ change, so no snapshot regeneration.