Skip to content

fix: require PR before merging to default branch#19

Merged
avrabe merged 1 commit intomainfrom
fix/require-pr-before-merge
Mar 7, 2026
Merged

fix: require PR before merging to default branch#19
avrabe merged 1 commit intomainfrom
fix/require-pr-before-merge

Conversation

@avrabe
Copy link
Contributor

@avrabe avrabe commented Mar 7, 2026

Summary

  • Change required_pull_request_reviews from null to { required_approving_review_count: 0 }
  • Blocks direct pushes to main — all changes must go through a PR
  • Zero approvals required — sole developer can create and merge own PRs without deadlock

How it works

  • GitHub API treats any non-null required_pull_request_reviews object as "require a PR"
  • required_approving_review_count: 0 means no approvals needed
  • dismiss_stale_reviews and require_code_owner_reviews default to false
  • After deploy + next sync, all org repos will enforce this

Test plan

  • After merge & deploy, run /sync-all-repos to apply to all repos
  • Verify direct push to main is blocked
  • Verify PR merge works without approvals

🤖 Generated with Claude Code

Set required_pull_request_reviews with required_approving_review_count: 0
to block direct pushes to main while allowing merge without approvals.
Sole developer can create and merge own PRs without deadlock.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@avrabe avrabe merged commit 0c48a25 into main Mar 7, 2026
3 checks passed
@avrabe avrabe deleted the fix/require-pr-before-merge branch March 7, 2026 19:11
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