Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
Workflow runs on both push and pull_request · build
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 · build
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: trueWorkflow runs on both push and pull_request · lint
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 · lint
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: trueWorkflow runs on both push and pull_request · coverage
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 · coverage
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: 12 more config fixes with negligible recoverable minutes: timeouts, retention, path filters
No job timeout · build
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 · build
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'Third-party actions pinned to a mutable ref · build
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 @mainNo job timeout · coverage
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 · coverage
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 · dependabot-sync
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: 15Scheduled at the top of the hour · dependabot-sync
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: '14 0 * * 0' # was '0 0 * * 0' — any non-:00 minute avoids the herdScheduled workflow runs in forks · dependabot-sync
The schedule has no repository guard, so forks that enable Actions inherit the cron and burn their own minutes. Gate the job with `if: github.repository == 'owner/repo'`.
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latestThird-party actions pinned to a mutable ref · dependabot-sync
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/dependabot-sync.yml@<full-sha> # was @mainNo job timeout · lint
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 · lint
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'Third-party actions pinned to a mutable ref · lint
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 @mainCopy every fix as one block (9 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, dependabot-sync, 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
# Scheduled at the top of the hour (applies to: dependabot-sync)
on:
schedule:
- cron: '14 0 * * 0' # was '0 0 * * 0' — any non-:00 minute avoids the herd
# Scheduled workflow runs in forks (applies to: dependabot-sync)
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latest
# Third-party actions pinned to a mutable ref (applies to: dependabot-sync)
uses: charmbracelet/meta/.github/workflows/dependabot-sync.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 @mainEach snippet is representative. Merge into the named workflow files rather than pasting wholesale.
Live CI-health badge → 
[](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, 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.