What changed

GitHub added repository-level Copilot code-review outcome fields, including addressed comments and merged pull requests without later human change requests. Separate usage fields now flag missing client telemetry and IDE or extension versions below reporting minimums.

Why it matters

Enterprises can distinguish adoption from observable review outcomes and can identify reporting blind spots before using usage data for governance or investment decisions. The new fields still measure actions and telemetry, not code quality or causal impact.

What to do

Export a fixed one-day repository and user report, calculate addressed rates only from evaluated comments, isolate missing telemetry and outdated clients, and compare a sample of merged pull requests with human review findings before setting any target.

Caveat

A comment counts as addressed through several behaviors, bot pull requests can enter some totals, and null values are not zero. Users can appear in multiple telemetry-gap counts, and the API does not establish that Copilot caused a merge or improved quality.