ci(registry): auto-merge the weekly rebuild after a green gate#25
Conversation
The weekly rebuild has failed every run for over a month: it pushes the
registry-update/* branch fine, but the create-PR step was denied by the
"Allow GitHub Actions to create and approve pull requests" repo setting,
leaving orphan branches and no PR. (That setting is now enabled.)
Make the job fully hands-off while keeping a PR in the history:
- validate the rebuilt registry.sqlite inline (test_registry_router runs
against the real embedded file) so a broken rebuild never reaches main;
- open the PR, then squash-merge it directly. PRs opened by the built-in
token don't trigger CI (anti-recursion), so native --auto would wait
forever; the inline gate is the merge gate instead. Retry the merge to
ride out the post-create mergeability window;
- guard every conditional step with success() so a failed gate can't fall
through to open/merge.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
Warning Review limit reached
More reviews will be available in 35 minutes and 11 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The weekly rebuild has failed every run for over a month: it pushes the
registry-update/* branch fine, but the create-PR step was denied by the
"Allow GitHub Actions to create and approve pull requests" repo setting,
leaving orphan branches and no PR. (That setting is now enabled.)
Make the job fully hands-off while keeping a PR in the history:
- validate the rebuilt registry.sqlite inline (test_registry_router runs
against the real embedded file) so a broken rebuild never reaches main;
- open the PR, then squash-merge it directly. PRs opened by the built-in
token don't trigger CI (anti-recursion), so native --auto would wait
forever; the inline gate is the merge gate instead. Retry the merge to
ride out the post-create mergeability window;
- guard every conditional step with success() so a failed gate can't fall
through to open/merge.
Co-authored-by: Roberto <robertoecf@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 participant
What
Make the weekly registry rebuild fully hands-off (auto-merge) while keeping a PR in the history.
Why it was broken
Every weekly run has failed for >1 month. The branch pushes fine, but the create-PR step was denied:
That's the repo setting Allow GitHub Actions to create and approve pull requests — now enabled. Result was orphan
registry-update/*branches and no PR; the data only reachedmainvia manual PRs (#17, #21).What changed
registry.sqliteis checked bytest_registry_router.py(runs against the real embedded file) before anything merges — a broken/empty rebuild fails here and never reachesmain.--autowould wait forever — the inline gate is the merge gate instead. Merge retries to ride out the post-create mergeability window.success()guards on every conditional step so a failed gate can't fall through to open/merge.No PAT and no branch protection required.