Copilot often reviews code and leaves a comment or two and then updates again later to add comments... this is very annoying. It should post all the comments at once.

[agm1984]

Select Topic Area

Bug

Copilot Feature Area

PR Reviews

Body

In the GitHub UI, Copilot reviews PRs, and everything is fine until Copilot reports how many comments it has on the PR. For multiple members on my team, we are having an issue where Copilot says "finished reviewing and left 9 comments", but it actually only posts 1 or 2 comments. Then we try to get the PR merged and the reviewer is like "what about these Copilot comments", and we are like wtf, and we look at the PR and there is 7 additional comments on there.

It would be nice if Copilot could wait until all of its comments are ready before it leaves its review on the PR.

[modelguyzz]

It looks like Copilot publishes review comments as it completes different parts of its analysis, instead of waiting to post everything at once. That’s why the total count can show more comments than you initially see. As each review pass finishes, additional comments appear.

There isn’t currently a way to force Copilot to batch all comments into a single submission. This is just how the review workflow behaves right now.

[Farhxn-15]

Yeah, this behavior can definitely feel confusing during PR reviews. What you are seeing is not a bug so much as how Copilot processes and publishes review feedback.

Copilot does not generate the entire review in a single pass. It analyzes the PR in chunks and posts comments incrementally as analysis completes. That is why you might see one or two comments first, then additional ones appear later.

A few reasons it works this way:

• Large PRs are analyzed in segments to keep response times reasonable.
• Comments are posted as soon as a section finishes processing rather than waiting for the full analysis.
• This streaming style prevents long delays and timeouts on complex diffs.
• Additional findings can appear after deeper semantic analysis finishes.

So the “review finished” count you see initially reflects the current batch, not necessarily the final set of comments.

Why this becomes confusing in teams:

If reviewers merge quickly after the first comments appear, later feedback can be missed. This is especially noticeable when Copilot reports a small number first and adds more afterward.

Practical ways teams handle this

• Wait a short moment after Copilot posts before merging large PRs.
• Refresh the PR once to ensure all comments have appeared.
• Use branch protection rules requiring human approval, not only automated reviews.
• Encourage reviewers to scan the full conversation tab before merging.

Why Copilot does not wait to post everything

Holding comments untilhed output
It would delay feedback significantly on large PRs.

Streaming feedback allows developers to begin addressing issues sooner.

Possible future improvements

It would be helpful if the UI indicated that analysis is still in progress or showed a “finalized review” state. Providing clearer completion signals would reduce confusion.