Skip to content

Clarify administrator branch protection bypass #96

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
arjitj2 merged 2 commits into from
Sep 28, 2026
Merged

Clarify administrator branch protection bypass #96

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2d569df
docs: clarify administrator branch protection bypass
arjitj2 Sep 28, 2026
774ab7a
docs: name unchanged branch protection settings
arjitj2 Sep 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ To test an unreleased change, use a separate installation or a disposable worksp

Read [AGENTS.md](AGENTS.md) and [UPSTREAM.md](UPSTREAM.md) before editing. Keep one shared skill tree for Codex and Claude Code. Preserve upstream licenses and credit. Record intentional differences from Cursor in the [decision ledger](maintenance/upstream-ledger.json). Each fact has one owner in the [documentation ownership](AGENTS.md#documentation-ownership) map. Update that owner and link to it from other pages.

`main` is protected: changes land through pull requests, the `verify` check from GitHub Actions must be up to date on the head commit (including for the owner), and force pushes and deletion of `main` are blocked. External approvals are not required. The installed-parent evidence under [Validate a change](#validate-a-change) is maintainer policy, not a branch-protection gate.
`main` requires pull requests and a passing `verify` check from GitHub Actions on a branch that is up to date with `main`. Repository administrators can bypass those requirements, including pushing directly to `main` or merging without updating the PR branch first. The **Allow force pushes** and **Allow deletions** settings remain disabled. External approvals are not required. The installed-parent evidence under [Validate a change](#validate-a-change) is maintainer policy, not a branch-protection gate.

## Development tools

Expand Down
Loading