GitHub Copilot metrics

Track GitHub Copilot adoption and usage across your teams over time

Definitions

• Contributors = The number of team members who have created at least one pull request in the selected time period

• Copilot enabled = The number of team members with a GitHub Copilot license at some point during the selected time period.

• Enabled rate = Copilot enabled / Contributors

• Weekly active, avg. = The average number of weekly active Copilot users. Users who have any activity during a calendar week are considered active for that week.

  • Usage is based on these interactions:

    • Receiving a code suggestion in an IDE (Note: It counts even if you don't accept the suggestion)

    • Chatting with Copilot Chat in an IDE

    • Interacting with Copilot on a mobile device

    • Interacting with Copilot Chat for CLI

  • Users must have telemetry enabled in their IDE for their activity to be included.

  • Read more

• Active rate, avg. = Weekly active, avg. / Contributors

Examples

If you're looking at a team of 5 contributors and have the "last 14 days" timeframe selected:

• Copilot enabled: If the team has one member who has had a Copilot license for the entire last 14 days, one person who terminated their license during that time, and one person who got a license during that time, they're all counted as enabled users, making the total 3. If someone has had a license but terminated it more than 14 days ago, they are not counted.

• Enabled rate: 3 / 5 = 60%

• Weekly active, avg.: If 3 people were active in the first week and 1 person was active in the second week, that makes the weekly average 2.

• Active rate, avg.: 2 / 5 = 40%

Why they matter

AI coding tools like GitHub Copilot can significantly boost developer productivity. Track GitHub Copilot adoption and usage across your teams over time to know if your investment is paying off.

How to use them

See how many developers have GitHub Copilot enabled versus how many are actively using it in any time period. This makes it easy to spot adoption trends, identify teams leading the charge, and find unused licenses that might need attention.

You can also compare Copilot adoption against trends in productivity metrics. Are teams with higher adoption seeing faster pull request cycle times? Are they keeping batch sizes in check? Is collaboration increasing, or are more people working alone?

Use the insights to evangelize successful practices from early adopters to teams still getting started. Or identify unused licenses — maybe it’s time to invest in training or stop paying for seats that aren’t being used.

Where to find them

Navigate to Metrics / GitHub Copilot

To see these metrics, you must grant Swarmia read access to GitHub Copilot Business. You’ll get access to data from this point onward (no backfill of historical data). View instructions