GitHub Copilot Code Review Gets a Smarter Overview, Titled Findings, and Auto-Generated Commit Messages

GitHub keeps tightening the loop between AI code review and the humans who have to act on it. A September 18 changelog entry ships an improved Copilot code review experience — now generally available — that reorganizes how findings are presented, how they resolve themselves, and how accepted suggestions turn into commits.

An overview comment that tracks state over time

The headline change is a refreshed overview comment that shows Copilot’s current assessment of the pull request, the review effort level it used, and a summary of what it found. Findings are grouped into three buckets: Open for issues that haven’t been addressed yet (with a new label marking ones introduced by the latest commits), Resolved since last review for issues Copilot has validated as fixed, and Previously missed for issues a subsequent review caught in existing changes. That last category is the interesting one — it surfaces problems found on a re-review that were never commented anywhere else on the PR, so they can’t silently slip past.

Each finding carries a severity label and a link to the corresponding inline comment, and as new commits land and reviews are re-requested, the overview preserves the running history. The previous PR summary and per-file summaries stay available too. The net effect is that a reviewer opening a PR with several rounds of Copilot commentary can see at a glance what’s still outstanding instead of reconstructing it from a comment thread.

Titles, smarter auto-resolution, and commit messages

Every Copilot code review comment now gets a title concisely describing the finding. Those titles double as the labels in the overview comment’s issue list, so scanning a dozen findings becomes a matter of reading headlines rather than opening each thread.

Auto-resolution — which lets Copilot close its own comments when the underlying issue is fixed — got sharper in two ways. If you reply to a Copilot comment asking to leave the issue open, it now honors that reply. And when Copilot does resolve a comment based on your subsequent commits, it records a reason: Won’t Fix or Incorrect. That distinction matters for auditability — a team reviewing what the agent concluded can tell the difference between “you fixed it” and “the agent was wrong.”

Finally, committing a batch of eligible Copilot suggestions now produces an AI-generated commit title and optional description based on the selected changes, and batches can mix Copilot and non-Copilot comments while still getting the smart commit message. It’s a small quality-of-life win, but commit hygiene is exactly the kind of thing that degrades when developers accept AI suggestions in bulk.

This is the third beat in GitHub’s recent code-review push, following approval authority earlier in September and auto-resolution updates on September 11. The pattern is consistent: each iteration moves Copilot’s reviews from a pile of comments toward a review artifact that maintains its own state. For teams running Copilot code review at scale, the overview comment is the piece that makes the rest usable.