Repository navigation
feat: implement issue #1548 — pr-review: forced re-review dispatches die to sweep concurrency, then unforced sweeps skip 'already reviewed at head' with no verdict posted — PRs strand - #1558
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
🤖 CodeAnt AI — Review Status
|
|
ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing |
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. Important Approval pendingCodeRabbit has no unresolved comments, but it has not reviewed the latest commit. Use the checkbox below to review the latest commit. CodeRabbit will approve the changes if it finds no blocking issues.
📝 WalkthroughWalkthroughThe sweep now distinguishes canonical verdicts from head markers. Orphaned markers trigger forced re-dispatch, while completed verdicts suppress re-review. Tests cover orphan recovery, rate-limit retries, and normal unforced dispatches. ChangesOrphaned review recovery
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to The change is localized to review-sweep behavior and its tests; no actionable merge-blocking risk remains after the requested normal validation checks. Sequence Diagram(s)sequenceDiagram
participant Sweep as pr-review-sweep
participant Markers as Review markers
participant Dispatch as dispatch_review
participant Trigger as pr-review-trigger.yml
Sweep->>Markers: Inspect head marker and canonical verdict
Markers-->>Sweep: Return marker and verdict counts
Sweep->>Dispatch: Rescue orphan marker with force mode
Dispatch->>Trigger: Dispatch with force_review=true
Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 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.
Code Review
This pull request addresses issue #1548 by updating scripts/sweep-stuck-reviews.sh to detect and handle orphaned review markers—where a review run stamped the head SHA but crashed before posting a final verdict. These orphaned reviews are now re-dispatched with force_review=true to bypass idempotency checks. Corresponding tests have been added to tests/test_sweep_stuck_reviews.bats. The review feedback recommends improving a negative assertion in the tests by asserting that grep exits with exactly status 1 instead of using ! grep, which prevents false passes on unexpected execution errors.
Dev-Lead — review-changes (applied)Changes committed and pushed. |
Dev-Lead — fix-bot-comment (no-changes)Agent reasoning |
|
CI checks on this PR are still running. Once they complete, re-mention Posted by the donpetry-bot PR-review cascade. |
|
Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-08-20T03:59:51Z. |
Dev-Lead — fix-bot-comment (no-changes)Agent reasoning |
|
Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-08-20T04:18:16Z. |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
…die to sweep concurrency, then unforced sweeps skip 'already reviewed at head' with no verdict posted — PRs strand
5d10439 to
5030930
Compare
Dev-Lead — rebase (applied)Rebase completed and pushed. |
Superseded by automated re-review at
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-08-30T22:43:25Z. |
|
|
Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-08-30T22:53:36Z. |
Dev-Lead — fix-bot-comment (no-changes)Agent reasoning |



User description
Closes #1548
Implemented by dev-lead agent. Please review.
Summary by CodeRabbit
Bug Fixes
Tests
CodeAnt-AI Description
Rescue pull requests when a review started but never posted a decision
What Changed
Impact
✅ Fewer pull requests stranded without a review verdict✅ Automatic recovery after interrupted reviews✅ No duplicate retries for completed reviews💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.