Six GitHub Actions misconfigs that silently drain your CI minutes

A developer auditing 35 popular open-source repositories found that nearly all had at least one wasteful GitHub Actions configuration, with 32 of 35 lacking concurrency control and 33 of 35 missing job timeouts. Common issues include triggering duplicate runs on both push and pull_request events, failing to cancel outdated runs when new commits are pushed, and skipping dependency caching that could save 30–90 seconds per run. Running full test matrices on every pull request and omitting path filters so docs-only changes trigger complete CI pipelines were also identified as frequent culprits. Each problem has a targeted fix, such as scoping triggers, adding concurrency groups with cancel-in-progress, enabling built-in caching in setup actions, and setting per-job timeout limits. The author released a free scanner at gitspider.com that flags these patterns for any public repository without requiring installation.