LogoLogo
Book a demoLog in
  • Swarmia documentation
  • Getting started
    • Get started in 15 minutes
    • Integrations
      • GitHub
        • GitHub Enterprise Server
        • Multiple GitHub organizations
        • Forked repositories
        • Troubleshooting
          • Reinstalling the Swarmia GitHub app
          • Updating app permissions
          • Installing Swarmia outside of GitHub Marketplace
      • Jira
        • Jira Server and Jira Data Center
        • Multiple Jira organizations
        • Limiting Jira project access
        • Troubleshooting
      • Linear
        • Private Linear teams
        • Disconnect Linear
      • Slack
        • Private Slack channels
      • Authentication
        • Google Single Sign-On
          • Frequently asked questions
        • Okta Single Sign-On
      • HR systems
      • Data export
        • Data cloud
        • Export data as a CSV file
      • Other integrations
        • Other issue tracker integrations
        • Other source code hosting integrations
  • Configurations for data quality
    • Teams & members
      • Creating & managing teams
        • Teams API
      • Contributors
      • Roles and permissions
      • Inviting team members
    • Issue tracker configuration
      • Jira configuration
      • Jira best practices
      • Linear configuration
    • Pull request exclusions
    • Linking pull requests to issues
    • Investment categories
    • Deployments
      • Generate deployments from merged pull requests
      • Generate deployments from GitHub deployments
      • Generate deployments from GitHub checks
      • Generate deployments via the API
        • Generate deployments for monorepos via the API
    • Sprint configuration
  • Use cases
    • Improve pull request flow
      • Pull request insights
      • Reducing pull request cycle time
      • Review code faster
      • Managing pull requests in progress with the Pull Request view
      • Diagnosing low pull request throughput
      • Analyzing pull request batch size
  • Improve your team's focus
    • Optimizing issue cycle time
    • Analyzing activity patterns on Work Log
    • Grouping activity on the Work Log view
    • Focus summary
  • Balance engineering investments
    • Activity and effort-based models
    • Categorizing work
    • Common problems with balancing engineering investment
  • Deliver strategic initiatives
    • Forecasting initiatives
  • Capitalize software development costs
  • Run developer experience surveys
    • Creating a survey
    • Managing surveys
    • Viewing and sharing survey results
    • How we show your survey responses
    • Survey communication guide and templates
  • Track DORA metrics
    • Automatic change failure detection
    • How Swarmia links PRs to deployments
  • Coach software developers
  • Get visibility into your CI pipeline
  • Continuous improvement
    • Working agreements
  • Notifications
    • Team notifications
    • Personal notifications
  • Notes
  • Retrospectives with Swarmia
  • Metrics & definitions
    • Pull request cycle time
      • What's the difference between "Change lead time" and "Pull request cycle time" metrics in Swarmia?
    • Issue cycle time
      • Defining issue lifecycle and cycle time
    • Developer effort (FTEs)
  • DORA metrics
    • Change lead time
    • Deployment frequency
    • Mean time to recovery
    • Change failure rate
  • Throughput
  • Time to deploy
  • Batch size
  • Flow efficiency
  • Scope creep
  • Sprints
  • GitHub Copilot metrics
  • Frequently asked questions
    • How do you treat weekends in metrics?
    • Tracking squashed commits
    • How do merge queues affect my metrics?
    • Why is my commit not visible in Swarmia?
    • How do I account for people leaving my organization?
  • Resources
    • Security & data retention
      • Data security
      • Data access
      • Swarmia IP Addresses
      • Single Sign-On (SSO) / SAML
      • Can I get a copy of the SOC 2 Type II audit report?
      • Deleting your organization
  • Pricing & plans
    • Compare plans
    • Free plan
    • Do I need a credit card to start a free trial?
    • What are the differences between the individual modules and the standard plan?
    • How do you determine the number of developers for billing?
    • What happens to customers with the Lite plan after the December 2024 pricing and plan change?
  • Changelog
On this page
  • Definitions
  • Examples
  • Why they matter
  • How to use them
  • Where to find them

Was this helpful?

GitHub Copilot metrics

Track GitHub Copilot adoption and usage across your teams over time

Definitions

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

  • Active users = The number of team members who have used GitHub Copilot at least once during the selected time period.

    • 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 considered

    • Read more

  • Enabled rate = The share or current team members who are enabled users.

  • Active rate = The share or current team members who are active users.

Examples

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

  • Enabled users: 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.

  • Active users: If the team has one member who has used Copilot every day for the past 14 days and another member who used it only once 13 days ago, they are both considered active users, making the total 2.

  • Enabled rate: 3 / 5 = 60%

  • Active rate: 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

PreviousSprintsNextFrequently asked questions

Last updated 15 days ago

Was this helpful?