ci(review): route reviews to GPT-5.6 tiers - #39
Conversation
|
Warning Review limit reached
Next review available in: 40 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 Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe PR makes fast and deep review models configurable through repository variables. Python defaults apply when variables are empty or unset. LiteLLM credentials are passed to the workflow, and routing and security tests were added. ChangesPR review model routing
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@tests/test_pr_review_routing.py`:
- Around line 5-10: Reorder the imports in the test module’s top-level import
block to match Ruff’s I001 sorting rules, preserving all existing imports and
functionality.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: e5abde73-ba0f-4c9d-9e92-4d85c917619b
📒 Files selected for processing (3)
.github/workflows/pr-review.yamlscripts/pr-review.pytests/test_pr_review_routing.py
e98ea1e to
929003b
Compare
929003b to
c3707ee
Compare
Route ordinary PR reviews to GPT-5.6 Luna with low reasoning and deep reviews to GPT-5.6 Terra with medium reasoning. Centralize default selection in the runner, accept optional repository-variable overrides, harden trusted workflow invocation, and add regression coverage for routing and API-response failures.
Summary by CodeRabbit
Improvements
Security
Tests