Repository navigation
chore(OMN-14077): drop onex_change_control from queue-repo automation lists - #1862
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 32 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
| Verdict | Meaning | Blocks merge? |
|---|---|---|
passed |
No critical/error findings | No |
blocked |
CRITICAL or ERROR findings found | Yes |
degraded |
All models unavailable (infra) | No (pilot) |
Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8524)
… lists OCC merge queue (ruleset 16846914) was disabled 2026-07-06 to relieve the deepest CI jam (OCC was 13-14 entries deep, evidence-companion PRs only). onex_change_control is now non-queue; remove it from: - armed_not_enqueued.py QUEUE_REPOS — otherwise every armed OCC PR is false-flagged as 'armed but not enqueued' (no queue to enqueue into). - cron-merge-sweep.sh ONEX_QUEUE_REPOS queue-heal default — the method-mismatch heal does not apply to a non-queue repo. Update the QUEUE_REPOS coverage test to the 6-repo set. OCC PRs now merge via the direct squash path (gh pr merge --squash --auto).
dafc9a7 to
70b8236
Compare
What
Drop
onex_change_controlfrom the merge-queue automation repo lists (OMN-14077). Its merge queue (ruleset16846914) was disabled on 2026-07-06 to relieve the deepest CI jam; OCC is now non-queue and merges via the direct squash path.Changes
plugins/onex/skills/_bin/_lib/armed_not_enqueued.py— removeOmniNode-ai/onex_change_controlfromQUEUE_REPOS. Otherwise every armed OCC PR is false-flagged as "armed but not enqueued" (there is no queue to enqueue into). Docstring example updated to match.scripts/cron-merge-sweep.sh— removeonex_change_controlfrom theONEX_QUEUE_REPOSqueue-heal default; the method-mismatch heal does not apply to a non-queue repo.tests/unit/skills/bin/test_armed_not_enqueued.py— update theQUEUE_REPOScoverage assertion to the 6-repo set + assert OCC absent.The enqueue path already degrades gracefully on a missing queue (
merge_queue_enqueue.py::is_no_merge_queue_error), so nothing hard-breaks in the interim; this change removes the wasted probes and the armed-not-enqueued false-flags.Verification (local)
uv run pytest tests/unit/skills/bin/test_armed_not_enqueued.py→ 33 passed.uv run ruff check+ruff format --checkclean on changed files.bash -n scripts/cron-merge-sweep.sh→ OK.Ref: OMN-14077 (under OMN-13979 / Lever 1b of
docs/plans/2026-07-06-ci-streamlining-logjam-reduction-plan.md).Evidence-Source: OCC#3663
Evidence-Ticket: OMN-14077