Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
Missing dependency cache · CI of mc_rtc
Set `bundler-cache: true` on `ruby/setup-ruby`, or add an `actions/cache@v4` step keyed on `Gemfile.lock`.
- uses: ruby/setup-ruby@v1
with:
bundler-cache: trueWorkflow runs on both push and pull_request · CI of mc_rtc
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 · Package mc_rtc
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 · Sync with GitLab
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: 8 more config fixes with negligible recoverable minutes: timeouts, retention, path filters
No job timeout · CI of mc_rtc
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) · CI of mc_rtc
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 of mc_rtc
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 - Nix
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) · CI - Nix
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-latestNo job timeout · Package mc_rtc
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 · Sync with GitLab
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) · Sync with GitLab
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 (7 snippets, annotated per workflow)
# Missing dependency cache (bundler) (applies to: CI of mc_rtc)
- uses: ruby/setup-ruby@v1
with:
bundler-cache: true
# Workflow runs on both push and pull_request (applies to: CI of mc_rtc, Package mc_rtc)
on:
push:
branches: [main]
pull_request:
# No concurrency control (applies to: Sync with GitLab)
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# No job timeout (applies to: CI of mc_rtc, CI - Nix, Package mc_rtc, Sync with GitLab)
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15
# Premium runners (macOS / Windows) (applies to: CI of mc_rtc, CI - Nix)
jobs:
build:
runs-on: ubuntu-latest # ~10x cheaper than macos-latest
# System packages reinstalled every run (applies to: CI of mc_rtc)
- uses: awalsh128/cache-apt-pkgs-action@latest
with:
packages: <your packages>
version: 1.0
# Full-history clone (fetch-depth: 0) (applies to: Sync with GitLab)
- 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/jrl-umi3218/mc_rtc)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.