Skip to content

chore(settings): require an approval of the latest push on protected branches - #16

Merged
Markeli merged 1 commit into
mainfrom
chore/require-pr-approval
Oct 4, 2026
Merged

Markeli merged 1 commit into
mainfrom
chore/require-pr-approval

Conversation

@Markeli

@Markeli Markeli commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

What

settings/rulesets/default-branch-pull-requests.json: required_approving_review_count 0 → 1 and require_last_push_approval → true for the default branch and release/*.

Why

The markeli-agent bot now opens pull requests with write access (e.g. in Curiosus.Migrations). With zero required approvals it could merge its own pull requests; with last-push approval it also can't push after a review and merge. Repository admins keep the bypass, so the owner's own pull requests still merge with "bypass rules". Sync and Dependabot pull requests are merged by hand already, nothing auto-merges.

After merge

scripts/repo-settings.py apply with admin rights, then scripts/repo-settings.py check.

🤖 Generated with Claude Code

…branches

The markeli-agent bot opens pull requests with write access; one approval of the
latest push keeps it from merging its own changes, including commits pushed
after a review. Repository admins keep the bypass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Markeli
Markeli enabled auto-merge October 4, 2026 16:40
@Markeli
Markeli merged commit deec677 into main Oct 4, 2026
5 checks passed
@Markeli
Markeli deleted the chore/require-pr-approval branch October 4, 2026 16:40
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