# GitHub — Track Copilot code review outcomes in Repository insights

- Company: GitHub (github.com)
- Announced: 2026-11-17T18:00:35+00:00
- Category: capability-change
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://github.blog/changelog/2026-11-17-track-copilot-code-review-outcomes-in-repository-insights
- Record: https://forck.live/items/37454-track-copilot-code-review-outcomes-in-repository-insights
- Subject: Copilot

GitHub is giving repository owners a way to see how Copilot code review feedback lands, adding a Repository insights page as the first item in a repository's Insights tab. The page gathers four summary signals per repository: comments addressed, high-severity comments addressed, pull requests with no later human change request, and merged pull requests without Copilot review. GitHub says the metrics show whether developers act on Copilot code review feedback, whether human reviewers still request changes after Copilot reviews a pull request, and where merged work skips Copilot review entirely. Teams can use that to find repositories with coverage gaps and focus enablement where it will have the most impact, according to GitHub. The same metrics also appear in the enterprise and organization repository 1-day reports (repos-1-day) in the Copilot usage metrics API. Anyone with read access to a repository can view the outcomes on the Repository insights page, while the API reports are limited to enterprise owners and billing managers, organization owners, and holders of a custom organization or enterprise role granting the View Copilot Metrics permission. GitHub notes the Copilot usage metrics policy must be enabled for the functionality to work.

## Evidence

Verbatim from https://github.blog/changelog/2026-11-17-track-copilot-code-review-outcomes-in-repository-insights:

> You can now see how Copilot code review feedback lands in each repository. A new “Repository insights” page, the first item in a repository’s Insights tab, brings Copilot code review outcomes together in one place.
> 
> Repository insights show four summary signals for each repository:
> 
> Comments addressed: Copilot code review comments that were acted on.
> 
> High-severity comments addressed: High-severity Copilot code review comments that were acted on.
> 
> Pull requests with no later human change request: Pull requests reviewed by Copilot that didn’t receive a later change request from a human reviewer.
> 
> Merged pull requests without Copilot review: Merged pull requests that Copilot code review didn’t review.
> 
> You can also explore:
> 
> Addressed rate: The share of evaluable comments that were addressed, with its numerator, denominator, unevaluable exclusions, trend over time, and supported breakdowns.
> 
> Comment categories: The types of feedback Copilot code review leaves in the repository.
> 
> The same metrics are also available in the enterprise and organization repository 1-day reports ( repos-1-day ) in the Copilot usage metrics API.

---

Record: https://forck.live/items/37454-track-copilot-code-review-outcomes-in-repository-insights
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
