copilot

Copilot Code Review Metrics Now Track Active vs Passive

Copilot code review metrics now split active and passive user engagement. Admins can measure real adoption maturity instead of just coverage.

TL;DR

Copilot usage metrics now distinguish between active and passive code review engagement
Two new API fields: used_copilot_code_review_active and used_copilot_code_review_passive
Admins can now measure real adoption, not just coverage

Active vs. passive CCR tracking — API now returns separate signals for users who intentionally engage with Copilot code review (assigning it, requesting reviews, applying suggestions) versus those whose PRs are auto-reviewed via repo policy without interaction.
User-level daily and 28-day reports — Enterprise and organization admins can see CCR engagement broken down by user and time period, giving a clearer picture of adoption maturity.
Precedence rule — If a user has both active and passive CCR events on the same day, the active signal takes precedence in the metrics.

Distinguish real engagement from coverage — you can now say "60% of users actively engage with CCR" instead of just "100% of repos are covered."
Sits alongside other Copilot surfaces — used_copilot_code_review_active and used_copilot_code_review_passive join used_agent (IDE agent mode) and used_copilot_coding_agent (CCA) for a complete adoption view.

Update via npm install @octokit/rest@latest or check the Copilot usage metrics API documentation.