Skip to content

ci: auto-merge OpenAPI sync PR past branch protection#288

Merged
prrao87 merged 1 commit into
mainfrom
chore/auto-merge-openapi-sync
Jun 29, 2026
Merged

ci: auto-merge OpenAPI sync PR past branch protection#288
prrao87 merged 1 commit into
mainfrom
chore/auto-merge-openapi-sync

Conversation

@prrao87

@prrao87 prrao87 commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

What

Adds --admin to the final gh pr merge in the OpenAPI sync workflow.

Why

The weekly OpenAPI sync PR was never auto-merging. The immediate gh pr merge call was rejected by main's base-branch policy:

Pull request #287 is not mergeable: the base branch policy prohibits the merge.

The merge API enforces branch protection (required broken-links-and-openapi check) for everyone unless a bypass is explicitly requested — so the green checks didn't matter, the call path itself was blocked.

Safety

  • The preceding gh pr checks --watch --fail-fast already confirms checks are green before the merge line is reached.
  • The bot token is an admin and only ever merges this one bot-generated sync PR.
  • No repo-level "Allow auto-merge" was enabled, so review/merge policy for all other PRs is unchanged.

🤖 Generated with Claude Code

The immediate `gh pr merge` was rejected by the base-branch policy
(required status check), since the merge API enforces branch protection
unless a bypass is requested. Checks are already confirmed green by the
preceding `gh pr checks --watch --fail-fast`, so the admin bot token can
safely bypass on the final merge call.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@prrao87 prrao87 merged commit a149609 into main Jun 29, 2026
2 checks passed
@prrao87 prrao87 deleted the chore/auto-merge-openapi-sync branch June 29, 2026 14:50
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