Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
Workflow runs on both push and pull_request · Publish Any Commit
Pushing to a branch and opening a PR triggers two runs. Pick one (usually `pull_request`) and exclude branch pushes for non-default branches.
on:
push:
branches: [main]
pull_request:No concurrency control · Close stale issues and PRs
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: 18 more config fixes with negligible recoverable minutes: timeouts, retention, path filters
No job timeout · Check Changelog
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 · Check Changelog
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'No job timeout · Close stale issues and PRs
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 · Close stale issues and PRs
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: '20 * * * *' # was '0 * * * *' — any non-:00 minute avoids the herdScheduled workflow runs in forks · Close stale issues and PRs
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 · Node Nightly CI
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) · Node Nightly 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-latestScheduled at the top of the hour · Node Nightly CI
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: '31 12 * * *' # was '0 12 * * *' — any non-:00 minute avoids the herdScheduled workflow runs in forks · Node Nightly CI
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 · Node CI
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 · Node 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'Premium runners (macOS / Windows) · Node 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-latestSystem packages reinstalled every run · Node CI
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.0Tests wrapped in auto-retry · Node CI
Tests run under an auto-retry wrapper, so each retry re-bills the same minutes and masks the flaky tests it papers over. Track, fix or quarantine the flakes, then drop the wrapper.
No job timeout · Publish Any 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 · Publish Any 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'cancel-in-progress on a deploy workflow · Publish Any Commit
This looks like a deploy/release workflow with `cancel-in-progress: true`, which cancels queued runs too, so a queued deploy is silently dropped when a newer run arrives. Use a group-only `concurrency:` block on deploys.
concurrency:
group: ${{ github.workflow }}
# queued deploys run in order; none are droppedNo job timeout · Require Changelog
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: 15Copy every fix as one block (10 snippets, annotated per workflow)
# Workflow runs on both push and pull_request (applies to: Publish Any Commit)
on:
push:
branches: [main]
pull_request:
# No concurrency control (applies to: Close stale issues and PRs)
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# No job timeout (applies to: Check Changelog, Close stale issues and PRs, Node Nightly CI, Node CI, Publish Any Commit, Require Changelog)
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15
# No path filters on triggers (applies to: Check Changelog, Node CI, Publish Any Commit)
on:
pull_request:
paths:
- 'src/**'
- 'package.json'
# Scheduled at the top of the hour (applies to: Close stale issues and PRs)
on:
schedule:
- cron: '20 * * * *' # was '0 * * * *' — any non-:00 minute avoids the herd
# Scheduled workflow runs in forks (applies to: Close stale issues and PRs, Node Nightly CI)
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latest
# Premium runners (macOS / Windows) (applies to: Node Nightly CI, Node CI)
jobs:
build:
runs-on: ubuntu-latest # ~10x cheaper than macos-latest
# Scheduled at the top of the hour (applies to: Node Nightly CI)
on:
schedule:
- cron: '31 12 * * *' # was '0 12 * * *' — any non-:00 minute avoids the herd
# System packages reinstalled every run (applies to: Node CI)
- uses: awalsh128/cache-apt-pkgs-action@latest
with:
packages: <your packages>
version: 1.0
# cancel-in-progress on a deploy workflow (applies to: Publish Any Commit)
concurrency:
group: ${{ github.workflow }}
# queued deploys run in order; none are droppedEach snippet is representative. Merge into the named workflow files rather than pasting wholesale.
Live CI-health badge → 
[](https://gitspider.com/scan/jestjs/jest)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.