Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
No concurrency control · Community
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: trueMissing dependency cache · Built-in Model Catalog
Set `cache: 'pip'` on your `actions/setup-python` step, or add an `actions/cache@v4` step keyed on your requirements/lock file.
- uses: actions/setup-python@v5
with:
python-version: '3.12'
cache: 'pip'Also found: 7 more config fixes with negligible recoverable minutes: timeouts, retention, path filters
No job timeout · Community
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 · Community
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 · Pull Request
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 · Pull Request
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 · Main
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 job timeout · Built-in Model Catalog
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: 15Full-history clone (fetch-depth: 0) · Built-in Model Catalog
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 hereCopy every fix as one block (5 snippets, annotated per workflow)
# No concurrency control (applies to: Community)
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# Missing dependency cache (pip) (applies to: Built-in Model Catalog)
- uses: actions/setup-python@v5
with:
python-version: '3.12'
cache: 'pip'
# No job timeout (applies to: Community, Pull Request, Main, Built-in Model Catalog)
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15
# No path filters on triggers (applies to: Community, Pull Request)
on:
pull_request:
paths:
- 'src/**'
- 'package.json'
# Full-history clone (fetch-depth: 0) (applies to: Built-in Model Catalog)
- uses: actions/checkout@v4
# fetch-depth: 0 removed — default shallow clone is enough hereEach snippet is representative. Merge into the named workflow files rather than pasting wholesale.
Live CI-health badge → 
[](https://gitspider.com/scan/vllm-project/semantic-router)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.