charmbracelet/bubbletea 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.

604 min/mo
recoverable (~26% of CI time) · across 14 patterns · ≈$4/mo
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 14 fixes, each with the exact YAML ↓
9.9%
failure rate, 30d
13h 44m
avg time to recover from a failure
Since : findings 22 → 14 · recoverable ~559 → ~604 min/mo
11 workflows · 223 runs (7.4/day) · 2,316 CI-min (wall-clock) · ≈$14 at private-repo rates (30d)

Where the minutes go (30d)

build~786 min · 68 runs
lint~779 min · 68 runs
coverage~742 min · 68 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Workflow runs on both push and pull_request · build

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

Workflow runs on both push and pull_request · lint

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

Workflow runs on both push and pull_request · coverage

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

No concurrency control · build

~79 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 concurrency control · lint

~78 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 concurrency control · coverage

~74 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: 8 more config fixes with negligible recoverable minutes: timeouts, retention, path filters

No job timeout · build

~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 path filters on triggers · build

~0 min/mo

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'

Full guide: how to fix this →

Third-party actions pinned to a mutable ref · build

~0 min/mo

3 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: charmbracelet/meta/.github/workflows/build.yml@<full-sha>  # was @main

No job timeout · coverage

~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 path filters on triggers · coverage

~0 min/mo

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'

Full guide: how to fix this →

No job timeout · lint

~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 path filters on triggers · lint

~0 min/mo

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'

Full guide: how to fix this →

Third-party actions pinned to a mutable ref · lint

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

uses: charmbracelet/meta/.github/workflows/lint.yml@<full-sha>  # was @main
Copy every fix as one block (6 snippets, annotated per workflow)
# Workflow runs on both push and pull_request (applies to: build, lint, coverage)
on:
  push:
    branches: [main]
  pull_request:

# No concurrency control (applies to: build, lint, coverage)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No job timeout (applies to: build, coverage, lint)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# No path filters on triggers (applies to: build, coverage, lint)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

# Third-party actions pinned to a mutable ref (applies to: build)
uses: charmbracelet/meta/.github/workflows/build.yml@<full-sha>  # was @main

# Third-party actions pinned to a mutable ref (applies to: lint)
uses: charmbracelet/meta/.github/workflows/lint.yml@<full-sha>  # was @main

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

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/charmbracelet/bubbletea