Guides
How to measure CI cost per pull request
You know the monthly total but not what a single pull request costs.
5 min read
You know the monthly total but not what a single pull request costs.
Why it happens
Billing is aggregated by account, not by change, so the unit economics are invisible.
How to fix it
- Sum job minutes by run and attribute runs to their pull request
- Multiply by the per-minute rate for each runner label
- Divide monthly spend by merged pull requests for a quick baseline
- Track the number over time — it is the metric that shows whether optimisation stuck
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to reduce GitHub Actions costsThe CI bill grows faster than the team and nobody is sure why.How to attribute CI cost to teamsCI spend is one line on the invoice and no team feels responsible for it.How to set a CI minutes budgetSpend is discovered at the end of the month rather than controlled during it.When larger runners actually save moneyA larger runner costs more per minute, so it is unclear whether it is cheaper overall.