Repository navigation
fix(server): pull request watch never wakes the agent about a replaced commit - #180
Conversation
yordis
commented
Oct 29, 2026
- A wake could describe checks or conflicts for a commit that had already been replaced by a newer push, sending the agent to fix problems that no longer exist.
- The agent needs to know which commit the findings are about so it can tell stale results from current ones.
PR SummaryMedium Risk Overview The watch reactor now always invalidates cached PR reads before each planned Conflict handling in Wake copy now states which short SHA the findings refer to and tells the agent to confirm the PR head is still that commit before acting. Tests cover invalidate-then-detail when fingerprint is null, conflict-on-replaced-head, the new message line, and reactor mocks that stub Reviewed by Cursor Bugbot for commit 2ea27de. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 21e8cf5. Configure here.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 39 minutes. View limit details
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 |
…d commit A cached read or a conflict carried over from an old head sent the agent after findings it had already pushed past. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
A conflict told about a replaced commit says nothing about the new head, so a push that fails to resolve it must be reported again. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
21e8cf5 to
2ea27de
Compare
