Skip to content

docs: no one can bypass the required checks, maintainers included #859

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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
irparent merged 1 commit into from
Oct 6, 2026
Merged

docs: no one can bypass the required checks, maintainers included #859

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 @@ -71,7 +71,7 @@ Match the formatting of the file you are editing. CI does not run Prettier, and

### What to expect after you open a PR

- **CI must pass.** Branch protection blocks merge until every required check is green. These are the exact context names, as GitHub reports them; the list is [`.github/required-checks.json`](.github/required-checks.json), which CI compares on every run with what the live settings require (branch protection and rulesets together):
- **CI must pass.** A ruleset blocks merge until every required check is green, and nobody can bypass it, maintainers included. These are the exact context names, as GitHub reports them; the list is [`.github/required-checks.json`](.github/required-checks.json), which CI compares on every run with what the live settings require (branch protection and rulesets together):

| Check | What it covers |
|---|---|
Expand Down
Loading