GitHub Actions on a private repo ran out of its included monthly compute — billed as a dollar amount, not raw minutes: $12/month on Free, $18/month on Team, $300/month on Enterprise Cloud. On a standard Linux runner at $0.006/minute that's roughly 2,000 / 3,000 / 50,000 minutes, but Windows ($0.010/minute) and macOS ($0.062/minute) runners burn through the same budget faster. Past that, workflows either bill per minute or stop running entirely if a spending limit is set. A self-hosted runner has no meter at all.
| Plan | Included compute/month | ≈ Minutes on standard Linux |
|---|---|---|
| Free | $12 USD | ~2,000 |
| Team | $18 USD | ~3,000 |
| Enterprise Cloud | $300 USD | ~50,000 |
Per-minute rate depends on runner OS and size: Linux 2-core is $0.006/minute (1-core slim is $0.002), Windows 2-core is $0.010/minute, and macOS is $0.062/minute — a macOS job burns through the included budget roughly ten times faster than the same job on Linux.
Settings > Billing > Actions usage to see exactly which workflow burned the minutes.concurrency: cancel-in-progress is a common silent cause.Registering a self-hosted runner — even on GitHub itself, with runs-on: self-hosted — removes those jobs from the minutes quota entirely, since the work runs on hardware you control instead of GitHub's shared pool. Rithub runs the identical .github/workflows/*.yml format on a self-hosted runner from day one — see GitHub Actions alternative, self-hosted and securing a self-hosted runner — so there's no quota to hit in the first place. The full migration path, not just CI, is in the migrate from GitHub to self-hosted git walkthrough.