Guides
The specific problems behind most GitHub Actions bills, with the exact change and how to verify it worked.
- Why your GitHub Actions bill is mostly macOS
macOS bills at roughly ten times the Linux rate. How to tell whether a job actually needs it, and the exact change if it does not. - Stop paying for GitHub Actions runs nobody waits for
Every push to a pull request starts a full run, even when a newer commit has already replaced it. The exact concurrency block that fixes it safely. - GitHub Actions cache not working: the usual causes
A cache that never hits is worse than no cache: it costs a cold run every time. The five causes, in the order worth checking.
Or let the scanner find it for you.
Read-only, no account for the first scan, and it prints the exact diff.