Harden review lineage stale reporting#688
Conversation
|
Warning Review limit reached
More reviews will be available in 2 minutes and 34 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (15)
✨ 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 |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9d0d31be9c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Use `lineage: "new"` when this is a first-time finding with no prior-round ancestor; omit `relates_to` unless a specific prior note helps. | ||
| Use `lineage: "deepening"` when the prior issue was valid but the current finding exposes a narrower or deeper edge case; set `relates_to` to the prior issue title or stable id when known. | ||
| Use `lineage: "repeat"` when the same issue still blocks the PR; set `relates_to` to the prior issue title or stable id when known. | ||
| Use `lineage: "stale"` when deterministic prior-round metadata shows the same reviewed HEAD or stale artifact is being evaluated again; set `relates_to` to the stale round, artifact, prior issue title, or stable id when known. |
There was a problem hiding this comment.
In automated review rounds, this instruction asks the reviewer to use lineage: "stale" only when deterministic prior-round metadata proves the same reviewed HEAD or a stale artifact, but the primary review prompt built by buildPrompt/formatPriorRoundContext only includes prior verdict text and not the current/prior head_sha or artifact identity; the new same-HEAD section is added later to the re-dispatch prompt after the reviewer has already emitted the verdict. As a result, normal reviewers have no allowed evidence to select stale, so the new stale lineage accounting and fail-closed behavior will be unreachable for the same-HEAD scenario unless a manual review file supplies it.
Useful? React with 👍 / 👎.
Relay Review Round 1Verdict: CHANGES_REQUESTED
|
Relay ReviewVerdict: LGTM |
1 participant
Summary
Verification
Fixes #682
Related #678