From the source
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.





