Skip to content

github mechanics

GitHub review comments stuck as pending: why nobody sees them, and how to submit

Othman Shareef · November 22, 2026 · 5 min read


If your GitHub review comments say pending and the author says they never saw them, you clicked Start a review and never submitted it. Pending comments are only visible to you. To send them, open the pull request’s Files changed tab, click Review changes, pick Comment, Approve or Request changes, and click Submit review. Every pending comment goes out at once, as one review.

Why nobody else sees them

GitHub’s docs on reviewing proposed changes say that before you submit your review, your line comments are pending and only visible to you. Nobody else gets a notification, the comments don’t show in the timeline, and the author has nothing to reply to. You can still edit them while they wait.

I’ve done this more than once, because the comment looks posted. It sits on the line in the diff with your avatar, and when you open the pull request again three days later nothing tells you loudly that it never went out.

Start a review vs Add single comment

When you write the first line comment on a pull request, GitHub offers two buttons:

  • Add single comment posts that one comment now. The author and anyone watching get notified.
  • Start a review opens a pending review and puts the comment in it. After that, the button on each new comment reads Add review comment, and everything you write joins the same review until you submit it.

Start a review exists for batching. GitHub’s commenting docs note that batching your comments avoids sending multiple notifications, and the Copilot cloud agent guide tells you to batch with Start a review instead of Add single comment, so the agent doesn’t start working on each comment before you’ve finished. It also gives you a verdict at the end, which a pile of single comments never does. For what each verdict means, see what a pull request review is.

Submitting a pending review

  1. Open the pull request and go to the Files changed tab.
  2. Above the changed code, click Review changes. Your pending comments are still on their lines, and you can edit them before you send anything.
  3. Type a summary of your feedback, or leave it short.
  4. Choose Comment, Approve or Request changes. Comment leaves feedback without approving or blocking.
  5. Click Submit review.

If you want none of it to go out, click Submit review, then Discard review. That cancels the pending review along with all of its comments, so copy anything worth keeping first.

Pending reviews in the API

In the REST API for pull request reviews, a review you create without an event stays in the PENDING state and has no submitted_at. The submit endpoint sends a pending review with an event such as APPROVE, REQUEST_CHANGES or COMMENT, and the delete endpoint removes a review that hasn’t been submitted. Submitted reviews can’t be deleted. A script that forgets the event leaves the same invisible review.

Habits that stop it happening

  • Pick the button by how many comments you plan to leave. One quick note gets Add single comment. A real pass through the diff gets Start a review.
  • Submit before you close the tab, even if you aren’t done reading. Three notes in a Comment review reach the author today, and you can start another review later.
  • When an author says they have no feedback from you, check Files changed for your own pending comments before you write them again.
  • Write each comment so it stands on its own once it lands. Review comments that land covers the wording, and suggested changes work inside a pending review like any other comment.

Pyor uses the same Start a review and Add single comment choice, and its review dock lists your Pending comments next to Submit review, so the unsent ones are hard to forget.

Frequently asked questions

Can the pull request author see my pending review comments?

No. GitHub says that before you submit your review, your line comments are pending and only visible to you. The author, other reviewers and anyone watching the pull request see nothing until you click Submit review.

What is the difference between Start a review and Add single comment?

Add single comment posts that one comment right away. Start a review holds the comment in a pending review, and every comment you add after it joins the same review until you submit it. GitHub recommends batching with Start a review when you plan to leave several comments, because it avoids a notification per comment.

How do I delete a pending review on GitHub?

Click Submit review, then Discard review. That cancels the pending review along with all of its pending comments. Through the REST API, the delete endpoint removes a review that has not been submitted; submitted reviews cannot be deleted.

Review your next PR in Pyor.

Pyor’s Focus menu jumps to active discussions, threads waiting on your reply, or unresolved comments. Free for individuals, and it talks to GitHub straight from your machine.