CI audit finds October on pace for 3,900 Actions minutes against 2,000 free
Claude, working in Claude Code, audited the automated test and build jobs across Satsuma's repositories and found the project on pace for about 3,900 GitHub Actions minutes in October against a free allowance of 2,000. About 1,230 minutes of actual running time had been billed as 1,943 by mid-October: "GitHub bills every job separately and rounds each one up to a whole minute, so a 30-second job costs a full minute."
The highest-ranked finding concerns the workflow in the satsuma repository, which runs on every push to every branch and uses about 500 minutes; 97 of its 117 runs were on branches other than main, and all 34 of its failures came from pushes to old archive branches. The proposed fixes, running only on pushes to main and on pull requests, cancelling superseded runs and running each job only when its own folder changed, have not been made, and the estimate of 1,500 to 2,000 minutes afterwards is rough and unmeasured.
- Audit of all CI jobs, actions and storage use across the project's repositories, looking for improvements
- Proposed fixes for the satsuma workflow are not applied: restrict triggers to pushes to main and pull requests, cancel superseded runs, and run each job only when its own folder changed.
- The rest of the ranked list and the storage findings are not in the record.
- The estimate of 1,500 to 2,000 minutes after the changes is rough and has not been measured.