Closed as not planned
Closed as not planned
Description
Problem
When CodeRabbit requests changes on a PR, the approval is removed (which is correct behavior). However, after the requested changes are fixed and resolved, the approval is not automatically restored. This leaves PRs in a limbo state where manual intervention is required to get approval back, even though all issues have been addressed.
Expected Behavior
After all requested changes are resolved, one of the following should happen:
- Auto-approval: Automatically restore approval when all requested changes are resolved
- Clear re-review mechanism: Provide a clear and streamlined way to trigger re-approval after fixes
Current Workaround
Users need to explicitly request a "full review" to trigger re-evaluation for approval.
Impact
This workflow issue affects development efficiency by:
- Leaving PRs stuck in limbo after fixes are applied
- Requiring additional manual steps to complete the review process
- Creating friction in the development workflow
References
- PR: cleanup and explicit use web prefix for protocols #4500
- Comment: cleanup and explicit use web prefix for protocols #4500 (comment)
- Reported by: @haslinghuis
Additional Context
This issue was identified during a cleanup PR where a requested change was fixed, but approval was not restored automatically, requiring explicit user intervention.