Connect GitHub to Xplorr: Actions, Packages and Copilot Spend
Connect GitHub to Xplorr
Section titled “Connect GitHub to Xplorr”GitHub is the bill engineering teams feel and nobody watches. It is not on your cloud invoice, and on a plan with an included allowance it fails loudly only once the allowance is gone: CI stops, and the invoice still reads zero.
Xplorr reads your organization’s billing usage and shows where it goes, by product, by SKU and by repository.
What you need
Section titled “What you need”- A GitHub organization (not a personal account)
- A token owned by an organization owner of that organization, with the permissions below
- Any Xplorr plan, including Free
Connect it
Section titled “Connect it”- In Xplorr, go to Cost Sources and find GitHub under Developer platforms.
- Enter your organization login, the name as it appears in your GitHub URL. For
github.com/acmethat isacme. - Paste a token with the permissions in Token permissions.
- Select Test connection. Xplorr calls the billing endpoint straight away, so a token without the right permission fails here rather than silently collecting nothing overnight.
- Save. The first sync runs on the next scheduled cycle.
Token permissions
Section titled “Token permissions”Use a fine-grained personal access token whose resource owner is the organization. GitHub’s names, as listed in its REST API reference:
| What Xplorr reads | Endpoint | Fine-grained token permission | Classic token scope |
|---|---|---|---|
| Billing usage (required) | GET /organizations/{org}/settings/billing/usage |
Administration organization permissions (read) | None documented in the REST reference |
| Copilot seats (optional) | GET /orgs/{org}/copilot/billing |
GitHub Copilot Business organization permissions (read), or Administration (read) | manage_billing:copilot or read:org |
The token’s owner matters as well as its permissions. GitHub’s REST reference says the billing usage endpoint needs an administrator of the organization (its billing guide names organization owners and billing managers), and only organization owners can read Copilot seat details. A token owned by an organization owner covers both.
Copilot is optional. Without Copilot access the billing usage still syncs, and only the seat counts are missing.
What Xplorr shows
Section titled “What Xplorr shows”Actions minutes by runner OS
Section titled “Actions minutes by runner OS”Runner cost is not uniform, and this is the single most useful thing the connector surfaces:
| Runner | Rate per minute |
|---|---|
| Linux | $0.0060 |
| Windows | $0.0100 |
| macOS | $0.0620 |
A macOS minute costs roughly ten times a Linux one. A single macOS entry in a build matrix is how an Actions bill triples, and no GitHub view puts those rates side by side.
Allowance consumed, not only what you were billed
Section titled “Allowance consumed, not only what you were billed”This is the number that matters on a plan with included minutes.
GitHub bills a gross amount, subtracts your included allowance, and charges the remainder. If the remainder is zero, the invoice is zero, and nothing tells you how close you are:
Actions Linux 4,981 minutes gross $29.89 allowance -$29.89 billed $0.00That organization had used its entire monthly allowance. Every invoice read zero until CI stopped with a billing error. Xplorr shows the consumed allowance so you can set a budget alert against it.
Spend per repository
Section titled “Spend per repository”Every usage line carries its repository, so you can see which repositories are consuming the estate’s minutes rather than only the total.
Copilot seats
Section titled “Copilot seats”If your organization uses Copilot, Xplorr records total seats against seats active in the current cycle. Inactive seats are a straightforward saving, in the same way an idle instance is.
What is not included
Section titled “What is not included”- Personal accounts. The billing endpoint is organization-scoped.
- Enterprise-level billing. Connect each organization separately.
- Per-user Actions attribution. GitHub bills Actions per repository, not per person. Copilot is the seat-based product, and that is reported per seat.
Troubleshooting
Section titled “Troubleshooting”“This token cannot read organization billing.” The token is valid but GitHub refused the billing usage endpoint. Give the token Administration organization permissions (read) for this organization, check that its owner is an organization owner, and test again.
“No organization named …”
Check the login is the organization’s, not a repository name or your username. For github.com/acme/api the organization is acme.
Connected, but no cost appears. An organization with no billable usage returns no rows, which is a real answer rather than a failure. Confirm on GitHub under Settings → Billing that the period you are looking at has usage.
Related
Section titled “Related”- Budget Alerts to be told before an allowance runs out
- Cost Allocation & Tags to group GitHub spend with the rest of your estate