You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(review): detect PR updates and prompt refresh #492
When reviewing a PR, the review session captures headSha at launch time. If the PR is updated (new commits pushed) while the review is open:
Submitting comments fails with HTTP 422 — GitHub rejects the review because commit_id doesn't match the current PR head
The diff is stale — the reviewer is looking at an old version of the code
There's no indication that the PR has changed
Proposed Solution
Poll the PR head SHA periodically (or use GitHub webhooks if available) and show an indicator in the header when the PR has been updated since the review was launched. Offer a "Refresh" action that re-fetches the diff, file contents, and PR context.
Considerations:
Polling interval (every 30-60s?)
What happens to in-progress annotations when refreshing?
Should the worktree (--local) be updated too?
Could also update headSha on refresh so comment submission works again
Context
Discovered during PR #491 development — pushed a fix commit while a review was open, then got a 422 when trying to submit comments.
Thanks for the report. I am consolidating the older backlog so related work has one current tracking issue.
This specific request is now tracked in #908 as part of the review freshness and VCS correctness work. During the June 13, 2026 older-than-two-month triage, I copied the relevant requirement from this issue into #908 and explained why it belongs with the related work.
I am closing this older issue so the backlog points at the current tracking issue. If there is a newer reproduction or a detail that is missing from #908, please comment there.
Activity
backnotprop commentedon Jun 13, 2026
Thanks for the report. I am consolidating the older backlog so related work has one current tracking issue.
This specific request is now tracked in #908 as part of the review freshness and VCS correctness work. During the June 13, 2026 older-than-two-month triage, I copied the relevant requirement from this issue into #908 and explained why it belongs with the related work.
I am closing this older issue so the backlog points at the current tracking issue. If there is a newer reproduction or a detail that is missing from #908, please comment there.