The Copilot usage metrics API now reports how many Copilot code review comments developers acted on, and how many reviewed PRs merged with no later human change request
GitHub adds an addressed rate for Copilot code review per repository, broken down by severity and by customization, so teams can see whether the review comments land.
// Key points
- New counts: comments evaluated, comments the developer acted on (applying the suggestion, asking Copilot to fix, editing the code, or replying the fix comes later), and merged PRs with no human change request after Copilot's first review
- Both counts are broken down by severity and by customization, such as custom instructions, skills, MCP servers or none
- Comments are evaluated when their pull request merges, so they count on the merge day; comments on PRs opened by bots such as Copilot cloud agent are usually not evaluated
- Available in enterprise and organization reports to owners, billing managers and custom roles with the permission; the Copilot usage metrics policy must be enabled
Builder's takeThis is the metric review bots have been missing: not how many comments, but how many anyone acted on. I'd pull it per repository for a month, compare repos with and without custom instructions, and cut the rules whose comments nobody addresses; note that bot-opened PRs are excluded, so agent PRs need their own measure.
// Background · from #Coding agents
Full timeline →- Nov 7 AWS runs Claude Code as a remote agent on Bedrock AgentCore: one microVM per task, up to three attempts, and a draft pull request unless verification passes
- Nov 7 Foundry Local runs Qwen3.8-27B at 4-bit in about 18 GB, on 24 GB consumer GPUs with up to 64K context, as a GitHub Copilot model provider
- Nov 6 Microsoft Research's PDD Kit turns intent into a Verus spec and proves agent-written code against it, verifying a Rust storefront's login logic