# GitHub — Usage metrics API adds code review details and addressed rate

- Company: GitHub (github.com)
- Announced: 2026-11-06T00:19:07+00:00
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://github.blog/changelog/2026-11-05-usage-metrics-api-adds-code-review-details-and-addressed-rate
- Record: https://forck.live/items/32433-usage-metrics-api-adds-code-review-details-and-addressed-rate
- Subject: Copilot

GitHub is adding code review detail to its Copilot usage metrics reports, so enterprise and organization owners can see whether developers act on Copilot code review feedback in each repository. A new copilot_code_review object on every repos-1-day row counts evaluated comments and the comments developers addressed, and dividing the two gives an addressed rate per repository. GitHub says the existing pull_requests fields only show how often Copilot code review runs and how often someone clicks to apply a suggestion, while developers act on most feedback in other ways. The counts are broken down by severity, review tier, comment type and customization, so teams can see whether custom instructions, skills or MCP servers make a difference. A further field counts merged pull requests that Copilot reviewed where no person requested changes after its first review. Comments are evaluated when their pull request merges, so they count on the merge day, and Copilot usually does not evaluate comments on pull requests opened by bots. Enterprise owners, enterprise billing managers, organization owners and holders of a custom role granting the View Copilot Metrics permission can access the reports, provided the Copilot usage metrics policy is enabled.

## Evidence

Verbatim from https://github.blog/changelog/2026-11-05-usage-metrics-api-adds-code-review-details-and-addressed-rate:

> The enterprise and organization repository-level Copilot usage metrics reports now show what happens to Copilot code review feedback. A new copilot_code_review object on each repos-1-day row 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. With these you can track an addressed rate per repository.
> 
> total_comments_evaluated : The number of Copilot code review comments checked to see whether the developer acted on them.
> 
> total_comments_addressed : The number of evaluated 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. Divide by total_comments_evaluated for the addressed rate.

---

Record: https://forck.live/items/32433-usage-metrics-api-adds-code-review-details-and-addressed-rate
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md