GitHub
Connect your GitHub organization to track Actions, Packages, Copilot, Codespaces, and storage costs.
What StackSpend tracks
Once connected, StackSpend imports the following cost categories from GitHub's billing API:
- Actions compute minutes
- Packages data transfer
- Copilot seat costs
- Codespaces compute
- Storage costs
Data updates daily.
Prerequisites
- A GitHub organization account — personal accounts are not supported by the billing API
- Organization owner or admin access
Setup
Create a Personal Access Token
Go to GitHub Settings → Developer settings → Personal access tokens → Tokens (classic).
Grant the following scopes:
admin:orgmanage_billing:enterprise— required if using GitHub Enterprisemanage_billing:copilot
Add to StackSpend
Go to Providers → Add provider → GitHub. Enter your organization name and the Classic PAT you just created. Click Save.
Verify
The first sync runs automatically after saving. Data updates daily in line with GitHub's billing API. Costs are tracked from your setup date — there is no historical backfill.
Data availability
| Property | Value |
|---|---|
| Latency | Daily |
| Historical data | From setup date only |
| Setup time | ~3 minutes |
Frequently asked questions
What credentials do I need to connect GitHub?
You need a GitHub Classic personal access token (PAT) with the admin:org and manage_billing:copilot scopes, created by an organization owner or admin. Fine-grained tokens do not support the org billing API, so you must use a Classic PAT.
Can I connect a personal GitHub account?
No. Only organization accounts are supported because GitHub's billing API does not expose personal account billing data. You must be an organization owner or admin to connect.
What GitHub costs does StackSpend track?
StackSpend imports Actions compute minutes, Packages data transfer, Copilot seat costs, Codespaces compute, and storage costs from GitHub's billing API. On the GitHub Business plan it also reads source control activity — deploys and pull requests — so a cost anomaly can be traced back to the PR or deploy behind it.
Is there historical backfill?
No. Costs are tracked from your setup date, and data updates daily in line with GitHub's billing API. There is no historical backfill, and free tier usage is automatically excluded so only paid usage appears in StackSpend.