Skip to content

chore: drop the required review count on main to 0 - #2

Merged
TGPSKI merged 1 commit into
mainfrom
chore/ruleset-review-count
Aug 4, 2026
Merged

chore: drop the required review count on main to 0#2
TGPSKI merged 1 commit into
mainfrom
chore/ruleset-review-count

Conversation

@TGPSKI

@TGPSKI TGPSKI commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Keeps the committed ruleset in sync with what GitHub is actually enforcing
(ruleset 20350835, applied live).

A 1-approval requirement on a solo-maintained repo means every change needs
gh pr merge --admin. Reaching for the override reflexively erodes the
protection more than lowering the count does.

Still enforced on main:

  • pull requests required
  • status checks must pass (Test (3.10), Test (3.14))
  • commits must be signed
  • no force-push, no deletion

require_code_owner_review and required_review_thread_resolution stay on, so
they take effect the moment there is a second maintainer.

A 1-approval requirement on a solo-maintained repo means every change
needs `gh pr merge --admin`, which trains you to reach for the override
reflexively -- that erodes the protection more than lowering the count
does.

The rules still doing real work stay: PRs are still required, status
checks must pass, commits must be signed, and main cannot be
force-pushed or deleted. Code-owner review and thread resolution remain
on, so they take effect the moment a second maintainer exists.

Applied live as ruleset 20350835; this commit keeps the file in the repo
matching what GitHub is enforcing.
@TGPSKI
TGPSKI merged commit c1c1f18 into main Aug 4, 2026
4 checks passed
@TGPSKI
TGPSKI deleted the chore/ruleset-review-count branch August 4, 2026 03:50
TGPSKI added a commit that referenced this pull request Aug 4, 2026
fork-only already carried RepositoryRole/5/always; main-ci, main-reviews and
release-tags-immutable did not. leather and skeptic carry it on all four, and
conceit now does too — this brings vanity in line.

Without it, main-reviews leans on required_approving_review_count: 0 to stay
workable on a solo repo (see #2), which weakens the rule for everyone rather
than exempting the one person who needs the exemption. The bypass is the
narrower tool.

release-tags-immutable is the one that actually bites: re-cutting a tag you
just found a defect in is impossible without it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant