Repository navigation
fix(ci): re-trigger auto-merge after review and checks complete [OMN-7786] - #1230
Conversation
…7786] The auto-merge workflow fired once at PR creation, before CodeRabbit posted its review. GitHub silently rejected the enable request when branch protection gates were pending, and continue-on-error hid the failure. By the time CodeRabbit finished and required_conversation_resolution cleared, no re-trigger existed, so merge-sweep had to re-enable auto-merge manually on every PR. - Add pull_request_review and check_suite triggers so the workflow re-attempts after review submission and CI completion - Add workflow_dispatch for manual recovery - Resolve PR number and author per event type (pull_request payload, check_suite.pull_requests, workflow_dispatch input) - Remove continue-on-error; tolerate benign "already enqueued" races via grep, surface real failures loudly - Gate on PR author login (pulled from resolved payload) instead of github.actor, which reflects the event actor, not the PR author
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 9 minutes and 6 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ 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)
Comment |
Summary
pull_request_reviewandcheck_suitetriggers so auto-merge re-attempts after CodeRabbit review and CI completion, closing the race where the workflow fires once at PR open before branch protection gates clear.continue-on-error; tolerate benign "already enqueued"/"clean" races via grep while surfacing real failures.workflow_dispatchfor manual recovery.Why
merge-sweep Track A has been re-enabling auto-merge by hand on every PR because the original workflow fired once at PR creation, silently failed when CodeRabbit hadn't reviewed yet, and never re-attempted.
Related: OMN-6571, OMN-5134
Test plan