ci: state mandatory structural exploration in reviews#349
Conversation
|
Warning Review limit reached
More reviews will be available in 52 minutes and 26 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. 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.
Pull request overview
This PR updates the OpenCode review text emitted by the opencode-review GitHub Actions workflow to make the repository’s “structural exploration” requirement explicit in both REQUEST_CHANGES and APPROVE review bodies, so reviews don’t appear acceptable when structural evidence is missing.
Changes:
- Add an explicit “Structural exploration” verification bullet to REQUEST_CHANGES review bodies.
- Add an explicit “Structural exploration completed / must not approve without it” verification bullet to APPROVE review bodies.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
1992402 to
b0de01d
Compare
OpenCode Review Overview
Pull request overviewThe changes in PR #349 are minimal and do not introduce any issues. The workflow update is safe and does not affect existing functionality. FindingsNo blocking findings from OpenCode's independent review. Verification
Gate evidence
|
There was a problem hiding this comment.
Pull request overview
The changes in PR #349 are minimal and do not introduce any issues. The workflow update is safe and does not affect existing functionality.
Findings
No blocking findings from OpenCode's independent review.
Verification
- Review source: independent OpenCode review of the current checkout, focused changed hunks, and current-head GitHub Check evidence.
- Structural exploration: completed before approval; if structural exploration, changed-file inspection, or evidence completeness is missing, OpenCode must not approve.
- Result: APPROVE
- Reason: No source-backed blockers found. Structural exploration completed.
Gate evidence
- Head SHA:
b0de01d481912d677c963dea55857cd14ed588a6 - Workflow run: 27743487442
- Workflow attempt: 1
|
Merge evidence for current head |
Summary
Verification
Security Notes