What changed
GitHub added REST and GraphQL management for Copilot code-review settings from enterprise to repository scope, explicit attribution and reported MCP or instruction sources for comments. Its impact dashboard and 28-day API reports now also show Copilot Chat and VS Code Agents-window engagement.
Why it matters
Administrators can automate review policy and distinguish Copilot output while measuring two previously hidden usage surfaces. The same update also clarifies that chat and agent-window use do not change adoption phases, preventing an analytics expansion from being mistaken for productivity evidence.
What to do
Export current review settings before using the APIs, apply one repository-level change with least-privilege credentials, verify attribution fields and source metadata, then baseline the new chat and VS Code agent metrics without comparing them directly with pre-change periods.
Caveat
The controls and metrics are GitHub product evidence, not proof that Copilot reviews improve code quality. Some settings endpoints exclude GitHub Apps and fine-grained tokens; the engagement rule counts two active days and users can appear in multiple features.