Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
No concurrency control · Console Integration
Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: trueNo concurrency control · Claude Code
Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: trueAlso found: 19 more config fixes with negligible recoverable minutes: timeouts, retention, path filters
Artifacts at default retention · CI
`upload-artifact` has no `retention-days`, so artifacts keep up to 90 days (storage cost). Set e.g. `retention-days: 7`.
- uses: actions/upload-artifact@v4
with:
name: build
path: dist/
retention-days: 7Premium runners (macOS / Windows) · CI
macOS bills ~10x and Windows ~2x a Linux minute. The cost estimate above assumes Linux, so your real spend is higher. Move any job that doesn't need them to `ubuntu-latest`.
jobs:
build:
runs-on: ubuntu-latest # ~10x cheaper than macos-latestThird-party actions pinned to a mutable ref · CI
4 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead. (21 more on a major-version tag like @v4; consider full-SHA pinning there too.)
uses: taiki-e/install-action@<full-sha> # was @nextestNo job timeout · Claude Code
No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15No job timeout · CodeQL
No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15No path filters on triggers · CodeQL
Runs on every push/PR with no `paths:` filter, so docs-only changes still trigger full CI. Add a `paths:` filter if that's common.
on:
pull_request:
paths:
- 'src/**'
- 'package.json'Scheduled at the top of the hour · CodeQL
The schedule fires at minute :00, GitHub's peak window, where scheduled runs get delayed or skipped. Shift to any other minute for the same cadence with less contention.
on:
schedule:
- cron: '29 6 * * 1' # was '0 6 * * 1' — any non-:00 minute avoids the herdScheduled workflow runs in forks · CodeQL
The schedule has no repository guard, so forks that enable Actions inherit the cron and burn their own minutes. Gate the job with `if: github.repository == 'owner/repo'`.
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latestNo job timeout · Console Integration
No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15No job timeout · Docs
No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15Large build matrix · Fuzz
The matrix expands to many parallel jobs per run, multiplying billable minutes, often more combos than you need. Trim the axes, or use `include:` to list only the combinations that matter.
strategy:
fail-fast: true
matrix:
include:
- { os: ubuntu-latest, node: 20 }
- { os: ubuntu-latest, node: 22 }Scheduled at the top of the hour · Fuzz
The schedule fires at minute :00, GitHub's peak window, where scheduled runs get delayed or skipped. Shift to any other minute for the same cadence with less contention.
on:
schedule:
- cron: '43 2 * * *' # was '0 2 * * *' — any non-:00 minute avoids the herdScheduled workflow runs in forks · Fuzz
The schedule has no repository guard, so forks that enable Actions inherit the cron and burn their own minutes. Gate the job with `if: github.repository == 'owner/repo'`.
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latestThird-party actions pinned to a mutable ref · Fuzz
2 third-party actions pinned to a branch or other mutable ref, which can change under you (supply-chain risk, non-reproducible builds). Pin to a full commit SHA instead. (2 more on a major-version tag like @v4; consider full-SHA pinning there too.)
uses: dtolnay/rust-toolchain@<full-sha> # was @nightlyNo path filters on triggers · Integration Tests
Runs on every push/PR with no `paths:` filter, so docs-only changes still trigger full CI. Add a `paths:` filter if that's common.
on:
pull_request:
paths:
- 'src/**'
- 'package.json'System packages reinstalled every run · Integration Tests
System packages install from the network on every run with no cache. Cache them (cache-apt-pkgs-action) or check whether the runner image already has the tool.
- uses: awalsh128/cache-apt-pkgs-action@latest
with:
packages: <your packages>
version: 1.0No job timeout · Supply Chain
No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15Scheduled at the top of the hour · Supply Chain
The schedule fires at minute :00, GitHub's peak window, where scheduled runs get delayed or skipped. Shift to any other minute for the same cadence with less contention.
on:
schedule:
- cron: '40 6 * * 1' # was '0 6 * * 1' — any non-:00 minute avoids the herdScheduled workflow runs in forks · Supply Chain
The schedule has no repository guard, so forks that enable Actions inherit the cron and burn their own minutes. Gate the job with `if: github.repository == 'owner/repo'`.
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latestCopy every fix as one block (13 snippets, annotated per workflow)
# No concurrency control (applies to: Console Integration, Claude Code)
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# Artifacts at default retention (applies to: CI)
- uses: actions/upload-artifact@v4
with:
name: build
path: dist/
retention-days: 7
# Premium runners (macOS / Windows) (applies to: CI)
jobs:
build:
runs-on: ubuntu-latest # ~10x cheaper than macos-latest
# Third-party actions pinned to a mutable ref (applies to: CI)
uses: taiki-e/install-action@<full-sha> # was @nextest
# No job timeout (applies to: Claude Code, CodeQL, Console Integration, Docs, Supply Chain)
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15
# No path filters on triggers (applies to: CodeQL, Integration Tests)
on:
pull_request:
paths:
- 'src/**'
- 'package.json'
# Scheduled at the top of the hour (applies to: CodeQL)
on:
schedule:
- cron: '29 6 * * 1' # was '0 6 * * 1' — any non-:00 minute avoids the herd
# Scheduled workflow runs in forks (applies to: CodeQL, Fuzz, Supply Chain)
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latest
# Large build matrix (applies to: Fuzz)
strategy:
fail-fast: true
matrix:
include:
- { os: ubuntu-latest, node: 20 }
- { os: ubuntu-latest, node: 22 }
# Scheduled at the top of the hour (applies to: Fuzz)
on:
schedule:
- cron: '43 2 * * *' # was '0 2 * * *' — any non-:00 minute avoids the herd
# Third-party actions pinned to a mutable ref (applies to: Fuzz)
uses: dtolnay/rust-toolchain@<full-sha> # was @nightly
# System packages reinstalled every run (applies to: Integration Tests)
- uses: awalsh128/cache-apt-pkgs-action@latest
with:
packages: <your packages>
version: 1.0
# Scheduled at the top of the hour (applies to: Supply Chain)
on:
schedule:
- cron: '40 6 * * 1' # was '0 6 * * 1' — any non-:00 minute avoids the herdEach snippet is representative. Merge into the named workflow files rather than pasting wholesale.
Live CI-health badge → 
[](https://gitspider.com/scan/pilotspace/moon)Want this on every push?
This scorecard is a one-time snapshot. Install the free GitHub App to track this repo continuously: new regressions caught as they land, trends over time, on your public and private repos. Team adds the offending commit on the PR + Slack alerts.
Install & monitor this repo →💬 On Team, this same analysis posts automatically to every PR: the regression, and the exact commit that caused it, right where your team already looks. See plans →
Not ready to install? Get this report by email. No spam, unsubscribe anytime.