storybookjs/storybook 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 min/mo
recoverable (~3% of CI time) · across 15 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 15 fixes, each with the exact YAML ↓
0.2%
failure rate, 30d
2h 51m
avg time to recover from a failure
Since : findings 17 → 15 · recoverable ~3 → ~1 min/mo
43 workflows · 2,500 runs (83.3/day) · 36 CI-min (wall-clock) · ≈$0 at private-repo rates (30d)
CI minutes, cost and failure rate are from the latest 500 of 2,500 runs.

Where the minutes go (30d)

Show cancelled CircleCI jobs as pending~12 min · 313 runs
Danger JS~9 min · 32 runs
Update Canary PR Body~3 min · 18 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · Show cancelled CircleCI jobs as pending

~1 min/mo

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

Full guide: how to fix this →

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

No job timeout · Agent eval

~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 →

Scheduled at the top of the hour · Agent eval

~0 min/mo

The schedule fires at minute :00, GitHub's peak window, where scheduled runs get delayed or skipped. Shift to any other minute for the same cadence with less contention.

on:
  schedule:
    - cron: '46 8 * * 1'  # was '0 8 * * 1' — any non-:00 minute avoids the herd

Full guide: how to fix this →

No job timeout · Show cancelled CircleCI jobs as pending

~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 →

No job timeout · Claude Code Review

~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 →

No concurrency control · Claude Code

~0 min/mo

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

Full guide: how to fix this →

No job timeout · Claude Code

~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 →

No job timeout · Danger JS

~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 →

No job timeout · Update Canary PR Body

~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 →

Missing dependency cache · Publish Canary Packages

~0 min/mo

Set `cache: 'yarn'` on your `actions/setup-node` step, or add an `actions/cache@v4` step keyed on your lockfile.

- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'yarn'

Full guide: how to fix this →

No job timeout · Publish Canary Packages

~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 →

cancel-in-progress on a deploy workflow · Publish Canary Packages

~0 min/mo

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 dropped

Full guide: how to fix this →

No job timeout · Triage issues

~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 →

No job timeout · Trigger CircleCI workflow

~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 →

No job timeout · GitHub Actions Security Analysis with zizmor 🌈

~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 →

Copy every fix as one block (5 snippets, annotated per workflow)
# No concurrency control (applies to: Show cancelled CircleCI jobs as pending, Claude Code)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No job timeout (applies to: Agent eval, Show cancelled CircleCI jobs as pending, Claude Code Review, Claude Code, Danger JS, Update Canary PR Body, Publish Canary Packages, Triage issues, Trigger CircleCI workflow, GitHub Actions Security Analysis with zizmor 🌈)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Scheduled at the top of the hour (applies to: Agent eval)
on:
  schedule:
    - cron: '46 8 * * 1'  # was '0 8 * * 1' — any non-:00 minute avoids the herd

# Missing dependency cache (yarn) (applies to: Publish Canary Packages)
- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'yarn'

# cancel-in-progress on a deploy workflow (applies to: Publish Canary Packages)
concurrency:
  group: ${{ github.workflow }}
  # queued deploys run in order; none are dropped

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/storybookjs/storybook.svg)](https://gitspider.com/scan/storybookjs/storybook)

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/storybookjs/storybook