GitSpider

jrl-umi3218/mc_rtc GitHub Actions scorecard

Public GitHub Actions data, last 30 days. Updated .

Data sourced from public GitHub. GitSpider is not affiliated with or endorsed by this repository's owners. Request removal.

1,042 min/mo
recoverable (~20% of CI time) · across 12 patterns · ≈$6/mo
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 12 fixes, each with the exact YAML ↓
37.2%
failure rate, 30d
15h 49m
avg time to recover from a failure
Since : findings 0 → 12 · recoverable ~0 → ~1,042 min/mo
10 workflows · 137 runs (4.6/day) · 5,228 CI-min (wall-clock) · ≈$31 at private-repo rates (30d)

Where the minutes go (30d)

CI of mc_rtc~2,057 min · 39 runs
Package mc_rtc~1,711 min · 53 runs
CI - Nix~1,444 min · 34 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Missing dependency cache · CI of mc_rtc

~617 min/mo · ≈$4/mo

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: true

Full guide: how to fix this →

Workflow runs on both push and pull_request · CI of mc_rtc

~264 min/mo · ≈$2/mo

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:

Full guide: how to fix this →

Workflow runs on both push and pull_request · Package mc_rtc

~161 min/mo · ≈$1/mo

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:

Full guide: how to fix this →

Also found: 9 more config fixes with negligible recoverable minutes: timeouts, retention, path filters

No job timeout · CI of mc_rtc

~0 min/mo

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: 15

Full guide: how to fix this →

Premium runners (macOS / Windows) · CI of mc_rtc

~0 min/mo

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-latest

Full guide: how to fix this →

System packages reinstalled every run · CI of mc_rtc

~0 min/mo

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.0

Full guide: how to fix this →

Third-party actions pinned to a mutable ref · CI of mc_rtc

~0 min/mo

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: jrl-umi3218/github-actions/install-dependencies@<full-sha>  # was @master

No job timeout · CI - Nix

~0 min/mo

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: 15

Full guide: how to fix this →

Premium runners (macOS / Windows) · CI - Nix

~0 min/mo

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-latest

Full guide: how to fix this →

Third-party actions pinned to a mutable ref · CI - Nix

~0 min/mo

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: re-actors/alls-green@<full-sha>  # was @release/v1

No job timeout · Package mc_rtc

~0 min/mo

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: 15

Full guide: how to fix this →

Third-party actions pinned to a mutable ref · Package mc_rtc

~0 min/mo

2 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.

uses: jrl-umi3218/github-actions/.github/workflows/package-project.yml@<full-sha>  # was @master
Copy every fix as one block (8 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 job timeout (applies to: CI of mc_rtc, CI - Nix, Package mc_rtc)
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

# Third-party actions pinned to a mutable ref (applies to: CI of mc_rtc)
uses: jrl-umi3218/github-actions/install-dependencies@<full-sha>  # was @master

# Third-party actions pinned to a mutable ref (applies to: CI - Nix)
uses: re-actors/alls-green@<full-sha>  # was @release/v1

# Third-party actions pinned to a mutable ref (applies to: Package mc_rtc)
uses: jrl-umi3218/github-actions/.github/workflows/package-project.yml@<full-sha>  # was @master

Each snippet is representative. Merge into the named workflow files rather than pasting wholesale.

Add the badge to your README

Live CI-health badge → GitSpider badge

[![GitSpider](https://gitspider.com/badge/jrl-umi3218/mc_rtc.svg)](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, every PR gets an automatic comment when its CI run fails or runs slow, right where your team already looks. See plans →

Not ready to install? Get this report by email. No spam, unsubscribe anytime.

Share this scorecard: https://gitspider.com/scan/jrl-umi3218/mc_rtc