Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
No job timeout · Lock inactive closed issues
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 · Lock inactive closed issues
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: '23 0 * * *' # was '0 0 * * *' — any non-:00 minute avoids the herdScheduled workflow runs in forks · Lock inactive closed issues
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 · pre-commit
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 · pre-commit
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 · pre-commit
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 }}-No job timeout · Tests
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: 15Premium runners (macOS / Windows) · Tests
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-latestCache without restore-keys · Tests
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 }}-Copy every fix as one block (6 snippets, annotated per workflow)
# No job timeout (applies to: Lock inactive closed issues, pre-commit, Tests)
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15
# Scheduled at the top of the hour (applies to: Lock inactive closed issues)
on:
schedule:
- cron: '23 0 * * *' # was '0 0 * * *' — any non-:00 minute avoids the herd
# Scheduled workflow runs in forks (applies to: Lock inactive closed issues)
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latest
# No path filters on triggers (applies to: pre-commit)
on:
pull_request:
paths:
- 'src/**'
- 'package.json'
# Cache without restore-keys (applies to: pre-commit, Tests)
key: deps-${{ runner.os }}-${{ hashFiles('**/<lockfile>') }}
restore-keys: |
deps-${{ runner.os }}-
# Premium runners (macOS / Windows) (applies to: Tests)
jobs:
build:
runs-on: ubuntu-latest # ~10x cheaper than macos-latestEach snippet is representative. Merge into the named workflow files rather than pasting wholesale.
Live CI-health badge → 
[](https://gitspider.com/scan/pallets/flask)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.