GitHub Copilot Code Review Adds Progress Tracking and Batch Commit Messages
The generally available review update separates open, resolved and newly surfaced findings while generating commit text for eligible suggestion batches.
Edited by Tyronne Panaino
GitHub made a revised Copilot code-review experience generally available on September 18, adding a progress-oriented overview, more explicit finding states and generated commit messages for eligible batches of accepted suggestions. The update changes how developers follow an AI review across multiple commits, rather than introducing a new review model or making a claim about defect-detection accuracy.
For teams that ask Copilot to revisit a pull request after changes, the central improvement is continuity. GitHub says the refreshed overview shows Copilot's current assessment, the review effort level and a summary of its findings, while keeping earlier pull-request and per-file summaries available.
Review progress is grouped by state
The overview divides findings into open issues, items resolved since the previous review, and previously missed issues that a later review surfaced in existing changes. Each finding carries a severity and a link to its inline comment. Comment titles also provide short descriptions that feed the overview list.
As developers push more commits and request another review, the overview preserves progress and logs the findings. GitHub says Copilot can auto-resolve its own comments when subsequent changes address them. It also honours a reply asking that an issue remain open and records a resolution reason such as `Won't Fix` or `Incorrect` when it closes a comment.
The distinction between newly introduced and newly detected findings is useful but important. A previously missed item was not necessarily caused by the latest commit; it is something Copilot found later in changes that were already present. That framing can help reviewers avoid treating every new comment as a new regression.
Accepted suggestions get commit context
When a developer commits an eligible, complete batch of Copilot review suggestions, Copilot now generates a relevant commit title and an optional description based on the selected changes. GitHub says a batch may include non-Copilot comments and still receive the generated commit text.
This reduces the clerical step between accepting suggestions and recording the resulting change, but it does not remove review responsibility. The release note documents interface and workflow behaviour; it does not publish independent measurements of false positives, missed defects, review time or downstream code quality. Teams still need their own review policy and tests to decide whether a suggestion should be applied.
Status
Confirmed. GitHub says the workflow changes are generally available. Confidence is medium because the behaviour is documented by the product owner without independent outcome validation.
Sources
Update note: Last reviewed 2026-09-22. We will revise this post if GitHub changes availability or documents material limits to the review workflow.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.