Review Problems
This page is for users whose review cannot resolve or finish the intended pull request.The Pull Request Cannot Be Resolved
Pass a numeric pull-request number and confirm it exists in the current repository. Run:The Review Targets the Wrong Branch or Commit
Standalone review uses the pull request’s pushed head and its current base. Confirm the pull request has the expected head commit and base branch in GitHub. Push local commits before requesting standalone review. If a pull request was retargeted, fetch the new base and retry. A deleted or unreachable base can stop review because the diff cannot be established safely.A Cloud Review Comment Does Nothing
Post/prflow:review as a standalone comment on the pull request’s Conversation tab. Review-submission text and inline review comments are not subscribed trigger surfaces. The requester must be an authorized repository collaborator.
A Duplicate Review Was Suppressed
PRFlow suppresses a second review request while a fresh progress comment shows a review of the same head commit in flight. Wait for that run. Push a new commit before requesting review again if the pull-request head has changed.The Progress Comment Has No Verdict
Open the linked Actions run and inspect execution diagnostics for permission denials or an engine error. A failed run can flip the comment toReview failed. A configured backstop may post a bounded resume request, but it does not retry forever.
Fresh installs do not provide the old automatic Devflow Review status workflow. Do not add that status as a required check unless your repository deliberately retained and operates the legacy tier.