Back to rankings

GitHub Copilot Code Review Adds Comment Resolution Reasons

GitHub CopilotView original changelog

GitHub Copilot code review comments now include a resolution reason dropdown, letting developers explain why a comment was closed by choosing Addressed, Won't fix, or Incorrect. The selector sits next to the existing "Resolve conversation" button on every review comment. GitHub says the goal is to feed structured signal back to its product team for continuous improvement of Copilot's review suggestions.

Key Takeaways

  • Copilot code review comments now include a resolution reason dropdown with three options: Addressed, Won't fix, and Incorrect.
  • The new selector sits next to the existing "Resolve conversation" button, adding no extra steps to the resolution workflow.
  • This gives GitHub structured feedback signals beyond a simple thumbs up/down reaction on review comments.
  • The feature applies specifically to AI-generated review comments, not to standard human-authored review threads.
  • Recording why a suggestion was dismissed creates a lightweight audit trail of how teams handle Copilot's feedback across a pull request.
  • GitHub is expected to use this data to improve the accuracy of future Copilot code review suggestions.

Comment Resolution Reasons

GitHub Copilot code review now lets developers specify a reason when closing out one of its review comments, adding a small but meaningful layer of structure to how teams interact with AI-generated feedback.

A Dropdown Next to "Resolve Conversation"

When resolving a Copilot review comment, developers now see a dropdown menu with three options: Addressed, Won't fix, and Incorrect. This selector appears directly next to the "Resolve conversation" button at the bottom of the comment thread, so recording a reason takes no extra steps beyond the resolution action developers were already taking.

Why It Matters

Previously, closing a Copilot comment gave no indication of whether the suggestion was actually implemented, deliberately skipped, or simply wrong. That made it hard for both teams and GitHub to understand how often Copilot's suggestions were useful versus off-base. By capturing a resolution reason at the moment of dismissal, GitHub gains structured feedback it can use to improve the accuracy and relevance of future review suggestions, while teams get a lightweight audit trail of how AI feedback was actually handled across a pull request.

This is a small interface change, but it plugs directly into the feedback loop GitHub uses to tune Copilot's code review model over time.