Re-enable required PR review on main when project matures

[jurij]

Context

main branch protection currently has required pull request reviews disabled (removed 2026-06-13) because the project is in a very early state with a single maintainer. GitHub does not allow a PR author to approve their own PR (hard platform rule), so requiring 1 approval blocked the solo maintainer from merging their own work.

Still enforced today: required status checks (checks, macos, Analyze javascript-typescript, Analyze swift), enforce_admins, conversation resolution, no force-push / no deletion. Only the approval gate was dropped.

When to re-enable

Re-instate required review once any of these is true:

• A second maintainer / regular contributor joins (so approvals are actually possible)
• External contributor PRs start arriving
• Before cutting a public 1.0

How to restore

gh api -X PATCH repos/limehq/munkel/branches/main/protection/required_pull_request_reviews \
  -F required_approving_review_count=1 \
  -F dismiss_stale_reviews=true \
  -F require_code_owner_reviews=true \
  -F require_last_push_approval=false

(Or: Settings → Branches → main → "Require a pull request before merging" → "Require approvals: 1".)

Note

This also affects the OpenSSF Scorecard Code-Review check, which only counts approvals from a second human login. Re-enabling restores that signal.