Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Teams tasks

Copilot reviews: how many get addressed

Written November 6, 2026

GitHub's usage metrics API now reports code-review details and addressed rates. What the numbers measure, and what they still can't show.

What the API now reports

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.

The fields are present on every row of the enterprise and organization repos-1-day reports. Counts are 0 and arrays are empty when a repository had no Copilot code review activity that day. Access needs an enterprise owner, enterprise billing manager, organization owner, or anyone with a custom organization or enterprise role that grants the View Copilot Metrics permission — and the Copilot usage metrics policy must be enabled.

The counting rules change what the numbers mean

The companion change: telemetry and version gaps

A second changelog the same day adds fields that say how complete the underlying data is. New per-user fields appear in enterprise and organization user reports, and daily affected-user counts appear in enterprise and organization reports.

Three rules govern how to read these. A user can be counted in both counts, so do not add the two counts together. Do not add counts across days to count unique users — each count covers a single day. And null or omitted values mean the data is unavailable, not false or zero; days before this release have no values. A user can also meet every version minimum and still be missing telemetry, for example behind a proxy. Users without client telemetry still count as active, but their reports lack detail such as lines of code, feature breakdowns, and model breakdowns.

What the numbers still cannot show

Limits

Related playbooks

Sources

Back to: Small-team playbooks hub · Also: Review a pull request with a coding agent · Triage a backlog of issues with an agent · Decide whether Copilot should approve PRs