GitHub

Roiva writes these metric observations on each sync. Reference the key in a value formula to use this data in your ROI calculations.

Pull Requests

Copilot Usage

Billing & Spend

• Track merged PR volume and cycle time before and after deploying an AI coding assistant such as Copilot or Cursor
• Measure lines-of-code output per engineer per month as a productivity proxy
• Correlate AI coding tool adoption with repository velocity trends over time
• Use cycle time reduction as the primary ROI signal for AI-assisted development initiatives
• Attribute Copilot seat and AI-credit spend to the initiative it belongs to, so velocity gains are measured against real cost

1. In Roiva: Click Continue to Authorize — you will be redirected to GitHub to install the Roiva GitHub App
2. In GitHub: Select the organization and choose which repositories to grant access to (if the app is already installed there, choose Configure, then Save) — note that Copilot and cost metrics are organization-scoped, so a personal account produces pull request data only
3. In GitHub: Approve the authorization prompt — Roiva uses it to confirm your GitHub account can access the installation you just chose. GitHub only asks the first time
4. In GitHub: For Copilot metrics, enable the 'Copilot usage metrics' policy under your organization's Copilot settings — the API refuses to return data until this is switched on, even for organization owners
5. Back in Roiva: Your connection is created automatically — PR data, Copilot usage and GitHub spend will sync nightly
6. Back in Roiva: The connection page checks each step and says what's missing
7. Back in Roiva: Link this connection to an initiative on the Initiatives tab

• Grant access to all repositories for the broadest signal; you can scope data per-initiative using the object type selector
• Cycle time (hours from PR open to merge) is the strongest leading indicator of AI coding assistant ROI
• Compare a 3-month baseline period against the 3 months after tool rollout for a clean before/after view
• High additions_avg alongside lower cycle_time_avg suggests engineers are writing more code, faster
• Copilot usage metrics require GitHub Copilot Business or Enterprise on the connected organization, plus the organization's 'Copilot usage metrics' policy switched on
• Line items covered by your included free-tier allowance net to zero and are not booked as costs — they still appear in the spend metrics
• Cost metrics read GitHub's billing usage API, which needs organization-admin access and an organization on GitHub's enhanced billing platform
• Cost entries default to Copilot and AI-credit spend only; add github_products to the initiative link config to include Actions, Codespaces or Storage
• If you already book your GitHub invoice through QuickBooks, Xero, NetSuite, Brex or Ramp, that AP entry wins and the GitHub-native cost entry is skipped for that month, so the same spend is never counted twice