Closed as not planned
Closed as not planned
Description
Problem Description
When CodeRabbit requests changes in a PR review and the approval is removed, the approval is not automatically restored after the requested changes are resolved. This leaves PRs in an unclear state even after all issues have been addressed.
Current Behavior
- CodeRabbit reviews a PR and approves it
- CodeRabbit later requests changes (approval is removed)
- Developer fixes the requested changes
- PR remains without approval, requiring manual intervention to trigger re-review
Expected Behavior
Either:
- Auto-approval should occur when all requested changes are resolved, or
- There should be a clearer mechanism for re-approval after fixes are implemented
Impact
- PRs are left in limbo after fixes are applied
- Requires manual
@coderabbitai full review
commands to restore approval - Disrupts development workflow and creates friction
References
- Original PR: cleanup and explicit use web prefix for protocols #4500
- Discussion: cleanup and explicit use web prefix for protocols #4500 (comment)
Reported by: @haslinghuis
Metadata
Metadata
Assignees
Labels
No labels