GitHub Copilot usage metrics add code review feedback and addressed rate

GitHub has added code review details and an addressed rate to the Copilot usage metrics API. The enterprise and organization repository-level reports now show what happens to Copilot code review feedback in each repository.

Every repos-1-day row includes a new copilot_code_review object. It reports how many Copilot-reviewed pull requests merged without a later change request from a person, and how many Copilot code review comments developers acted on. The addressed rate is calculated from two counts. total_comments_evaluated is the number of comments checked to see whether the developer acted on them. total_comments_addressed is the number of those comments the developer acted on, whether by applying the suggestion, asking Copilot to make the fix, editing the code, or replying that the fix will come in a later pull request. Dividing addressed comments by evaluated comments gives the rate.

The object also breaks down both counts by severity, review tier, comment type, and customization. Comments are evaluated when their pull request merges, so they count on the merge day. Counts are zero and arrays are empty for repositories with no Copilot code review activity that day.

Why it matters

The existing pull_requests fields show how often Copilot code review runs and how often someone clicks to apply a suggestion. Developers often act on feedback in other ways, so those fields miss much of the impact. The new fields show which kinds of comments land, whether custom instructions, skills, and MCP servers make a difference, and whether reviewers still request changes after Copilot reviews.

What to do

Pull the repos-1-day reports for your enterprise or organization and calculate the addressed rate for each repository. Compare results across customization settings and comment types to see where Copilot feedback is most useful. Confirm availability and any plan requirements on GitHub’s site, since the source notes do not cover those details.