Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
Concurrency without cancel-in-progress · RunPod tenferro-rs GPU Test
Concurrency group has no `cancel-in-progress: true`, so superseded runs queue instead of cancelling. Add it to supersede stale runs.
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: trueAlso found: 13 more config fixes with negligible recoverable minutes — timeouts, retention, path filters
No path filters on triggers · CI_gpu
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 · CI PR workspace 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: 15No path filters on triggers · CI PR workspace 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'Full-history clone (fetch-depth: 0) · CI PR workspace tests
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 hereSystem packages reinstalled every run · CI PR workspace 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 · 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 · 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'Full-history clone (fetch-depth: 0) · CI
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 hereSystem packages reinstalled every run · 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.0No job timeout · Deploy Documentation
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 · Deploy Documentation
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 · Deploy Documentation
This looks like a deploy/release workflow with `cancel-in-progress: true`, which cancels queued runs too — 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 droppedSystem packages reinstalled every run · Deploy Documentation
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.0Copy every fix as one block (6 snippets, annotated per workflow)
# Concurrency without cancel-in-progress — applies to: RunPod tenferro-rs GPU Test
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# No path filters on triggers — applies to: CI_gpu, CI PR workspace tests, CI, Deploy Documentation
on:
pull_request:
paths:
- 'src/**'
- 'package.json'
# No job timeout — applies to: CI PR workspace tests, CI, Deploy Documentation
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15
# Full-history clone (fetch-depth: 0) — applies to: CI PR workspace tests, CI
- uses: actions/checkout@v4
# fetch-depth: 0 removed — default shallow clone is enough here
# System packages reinstalled every run — applies to: CI PR workspace tests, CI, Deploy Documentation
- uses: awalsh128/cache-apt-pkgs-action@latest
with:
packages: <your packages>
version: 1.0
# cancel-in-progress on a deploy workflow — applies to: Deploy Documentation
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.
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 →Not ready to install? Get this report by email. No spam, unsubscribe anytime.
Live CI-health badge → 
[](https://gitspider.com/scan/tensor4all/tenferro-rs)