Check your workflow for wasted minutes
Paste a GitHub Actions workflow. You get the settings that make runs longer or more numerous than they need to be, each with the change to make and the GitHub page that explains it.
Checked in your browser. Your YAML is not uploaded.
The seven checks
Each one comes from a page in GitHub's own documentation, linked beside it.
- A concurrency group that cancels superseded runs on pull requestsUsing concurrency
- How many jobs a matrix starts, and which operating systems are in itRunning variations of jobs in a workflow
- A shallow checkout where the job does not read historyactions/checkout, fetch-depth
- A cache for the packages a job installsCaching dependencies to speed up workflows
- timeout-minutes on every jobWorkflow syntax, timeout-minutes
- push and pull_request firing twice for one commitWorkflow syntax, on.push.branches
- Actions pinned to a version tag or a commitSecurity hardening, using third-party actions
This checker is ours: runners.io publishes it free, and we wrote the rules. It reads the settings in a workflow, not how long its steps take, so it can say what to change and why, and cannot put a number of minutes on it. A check that has nothing to look at, such as a matrix check on a workflow with no matrix, says so instead of passing.
The checker stays free. Connect GitHub when you want your runs on runners.io.
Card required. You pay only for the minutes your jobs run.