Track Copilot code review outcomes in Repository insights
GitHub added a Repository insights page that shows how Copilot code review feedback is landing in each repository. It's the first item in a repository's Insights tab.
Four summary signals sit at the top:
- Comments addressed: Copilot review comments that were acted on
- High-severity comments addressed: the same count, limited to high-severity comments
- Pull requests with no later human change request: PRs Copilot reviewed that no human reviewer later asked to change
- Merged pull requests without Copilot review: merged work that Copilot never reviewed
You can also open the addressed rate, which is the share of evaluable comments that were addressed. It shows its numerator, denominator, unevaluable exclusions, a trend over time, and supported breakdowns. A comment categories view shows the types of feedback Copilot leaves in the repository. The page puts these next to pull request activity and merge times, and the docs say the signals don't prove code is defect-free or that Copilot caused an improvement.
Anyone with read access to the repository can see the page, and it's available for organization-owned repositories. The Copilot code review section only appears if the organization has enabled both the Copilot usage metrics policy and the Copilot code review policy. The same metrics are also in the enterprise and organization repository 1-day reports (repos-1-day) in the Copilot usage metrics API. Enterprise owners, billing managers, organization owners, and anyone with a role that grants View Copilot Metrics can access those reports.