Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
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'Third-party actions pinned to a mutable ref · CI_gpu
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. (1 more on a major-version tag like @v4; consider full-SHA pinning there too.)
uses: dtolnay/rust-toolchain@<full-sha> # was @stableNo path filters on triggers · CI cache publish
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 · CI cache publish
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 · 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.0Third-party actions pinned to a mutable ref · CI PR workspace tests
5 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. (3 more on a major-version tag like @v4; consider full-SHA pinning there too.)
uses: dtolnay/rust-toolchain@<full-sha> # was @stableNo 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'Premium 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-latestSystem 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.0Third-party actions pinned to a mutable ref · CI
7 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. (6 more on a major-version tag like @v4; consider full-SHA pinning there too.)
uses: dtolnay/rust-toolchain@<full-sha> # was @stableNo 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, 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 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.0Third-party actions pinned to a mutable ref · Deploy Documentation
1 third-party action 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 @stableArtifacts at default retention · Oracle replay nightly
`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: 7Scheduled workflow runs in forks · Oracle replay nightly
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 · Oracle replay nightly
1 third-party action 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.
uses: dtolnay/rust-toolchain@<full-sha> # was @stableCopy every fix as one block (9 snippets, annotated per workflow)
# No path filters on triggers (applies to: CI_gpu, CI cache publish, CI PR workspace tests, CI, Deploy Documentation)
on:
pull_request:
paths:
- 'src/**'
- 'package.json'
# Third-party actions pinned to a mutable ref (applies to: CI_gpu, CI PR workspace tests, CI, Deploy Documentation, Oracle replay nightly)
uses: dtolnay/rust-toolchain@<full-sha> # was @stable
# Scheduled workflow runs in forks (applies to: CI cache publish, Oracle replay nightly)
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latest
# 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)
- 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
# Premium runners (macOS / Windows) (applies to: CI)
jobs:
build:
runs-on: ubuntu-latest # ~10x cheaper than macos-latest
# cancel-in-progress on a deploy workflow (applies to: Deploy Documentation)
concurrency:
group: ${{ github.workflow }}
# queued deploys run in order; none are dropped
# Artifacts at default retention (applies to: Oracle replay nightly)
- uses: actions/upload-artifact@v4
with:
name: build
path: dist/
retention-days: 7Each snippet is representative. Merge into the named workflow files rather than pasting wholesale.
Live CI-health badge → 
[](https://gitspider.com/scan/tensor4all/tenferro-rs)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.