Copilot code review user counts now aggregate in usage metrics API
Source: GitHub Changelog
Following the launch of Copilot code review active and passive user identification, enterprise and organization usage reports in the Copilot usage metrics API now include aggregated active and passive user counts for Copilot code review.
Six new fields are available in both 1‑day and 28‑day reports at the enterprise and organization levels:
| Field | Description |
|---|---|
daily_active_copilot_code_review_users | Active users who used Copilot code review on that day |
daily_passive_copilot_code_review_users | Passive users who used Copilot code review on that day |
weekly_active_copilot_code_review_users | Active users who used Copilot code review in the trailing 7‑day window |
weekly_passive_copilot_code_review_users | Passive users who used Copilot code review in the trailing 7‑day window |
monthly_active_copilot_code_review_users | Active users who used Copilot code review in the trailing 28‑day window |
monthly_passive_copilot_code_review_users | Passive users who used Copilot code review in the trailing 28‑day window |
Active users are those who manually requested a Copilot code review or applied a Copilot suggestion. Passive users are those whose reviews were auto‑triggered by a repository or organization policy, with no active signal in the same period. When a user has both active and passive signals, they are counted as active only—active always trumps passive.
Why this matters
- Distinguish adoption drivers – Separate intentional Copilot code review adoption from policy‑driven, auto‑triggered usage.
- Compare engagement across time windows – Daily, weekly, and monthly counts let you track active and passive adoption trends and measure the impact of rollout efforts.
- Make informed rollout decisions – Use the active‑versus‑passive breakdown to guide Copilot code review policies and investment.
Visit the Copilot usage metrics API documentation to learn more.
Join the discussion within the GitHub Community.