Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
Missing dependency cache · desktop-build
Add `Swatinem/rust-cache@v2` (the de-facto cargo cache), or an `actions/cache@v4` step keyed on `Cargo.lock`.
- uses: Swatinem/rust-cache@v2No concurrency control · labeler
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: 8 more config fixes with negligible recoverable minutes: timeouts, retention, path filters
No path filters on triggers · ci
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'Cache without restore-keys · ci
The cache restores only on an exact key match, so any lockfile change means a full cold download. Add a `restore-keys:` prefix line for partial restores.
key: deps-${{ runner.os }}-${{ hashFiles('**/<lockfile>') }}
restore-keys: |
deps-${{ runner.os }}-Scheduled 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-latestPremium runners (macOS / Windows) · desktop-build
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-latestNo path filters on triggers · gitleaks
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'Full-history clone (fetch-depth: 0) · gitleaks
checkout fetches the entire git history every run (`fetch-depth: 0`) and nothing in the workflow appears to read it. Remove the line; the default shallow clone is much faster on big repos. Keep it if a step genuinely needs history.
- uses: actions/checkout@v4
# fetch-depth: 0 removed — default shallow clone is enough hereNo path filters on triggers · labeler
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 workflow runs in forks · zizmor
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 (7 snippets, annotated per workflow)
# Missing dependency cache (cargo) (applies to: desktop-build)
- uses: Swatinem/rust-cache@v2
# No concurrency control (applies to: labeler)
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# No path filters on triggers (applies to: ci, gitleaks, labeler)
on:
pull_request:
paths:
- 'src/**'
- 'package.json'
# Cache without restore-keys (applies to: ci)
key: deps-${{ runner.os }}-${{ hashFiles('**/<lockfile>') }}
restore-keys: |
deps-${{ runner.os }}-
# Scheduled workflow runs in forks (applies to: codeql, zizmor)
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latest
# Premium runners (macOS / Windows) (applies to: desktop-build)
jobs:
build:
runs-on: ubuntu-latest # ~10x cheaper than macos-latest
# Full-history clone (fetch-depth: 0) (applies to: gitleaks)
- uses: actions/checkout@v4
# fetch-depth: 0 removed — default shallow clone is enough hereEach snippet is representative. Merge into the named workflow files rather than pasting wholesale.
Live CI-health badge → 
[](https://gitspider.com/scan/clezcoding/claredtool)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.