Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
Workflow runs on both push and pull_request · images
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:Workflow runs on both push and pull_request · CI
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:Docker build without layer cache · staging-smoke
The Docker build has no layer cache, so every run re-executes every layer from scratch. Add `cache-from: type=gha` / `cache-to: type=gha,mode=max` to the build step.
- uses: docker/build-push-action@v6
with:
cache-from: type=gha
cache-to: type=gha,mode=maxNo concurrency control · cluster-smoke
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: trueNo concurrency control · staging-smoke
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: 4 more config fixes with negligible recoverable minutes — timeouts, retention, path filters
Artifacts at default retention · CI
`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: 7No 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 }}-No path filters on triggers · staging-smoke
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'Copy every fix as one block (6 snippets, annotated per workflow)
# Workflow runs on both push and pull_request — applies to: images, CI
on:
push:
branches: [main]
pull_request:
# Docker build without layer cache — applies to: staging-smoke
- uses: docker/build-push-action@v6
with:
cache-from: type=gha
cache-to: type=gha,mode=max
# No concurrency control — applies to: cluster-smoke, staging-smoke
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# Artifacts at default retention — applies to: CI
- uses: actions/upload-artifact@v4
with:
name: build
path: dist/
retention-days: 7
# No path filters on triggers — applies to: CI, staging-smoke
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 }}-Each 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/carinrc/loom)