withastro/astro 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.

163 min/mo
recoverable (~9% of CI time) · across 31 patterns · ≈$1/mo
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 31 fixes, each with the exact YAML ↓
1.6%
failure rate, 30d
0m
avg time to recover from a failure
Since : findings 32 → 31 · recoverable ~201 → ~163 min/mo
31 workflows · 2,500 runs (83.3/day) · 1,761 CI-min (wall-clock) · ≈$11 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)

CI~884 min · 49 runs
Release~418 min · 15 runs
Continuous benchmark~120 min · 17 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Missing dependency cache · Release

~125 min/mo · ≈$1/mo

Set `cache: 'pnpm'` 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: 'pnpm'

Full guide: how to fix this →

Missing dependency cache · Factory preview release

~15 min/mo

Set `cache: 'pnpm'` 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: 'pnpm'

Full guide: how to fix this →

No concurrency control · Examples astro check

~11 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 · Semgrep OSS scan

~4 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 · GitHub Actions Security Analysis with zizmor 🌈

~3 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 · Diff Dependencies

~2 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 · Check mergeability

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

No concurrency control · Cleanup cache

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

No concurrency control · Label PRs

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

No job timeout · Check mergeability

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

Large build matrix · CI

~0 min/mo

The matrix expands to many parallel jobs per run, multiplying billable minutes, often more combos than you need. Trim the axes, or use `include:` to list only the combinations that matter.

strategy:
  fail-fast: true
  matrix:
    include:
      - { os: ubuntu-latest, node: 20 }
      - { os: ubuntu-latest, node: 22 }

Full guide: how to fix this →

Premium runners (macOS / Windows) · CI

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

Full-history clone (fetch-depth: 0) · CI

~0 min/mo

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 here

Full guide: how to fix this →

No job timeout · Cleanup cache

~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 · Cleanup cache

~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: '20 11 * * *'  # was '0 11 * * *' — any non-:00 minute avoids the herd

Full guide: how to fix this →

Scheduled at the top of the hour · PR: Close Duplicates

~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: '37 6 * * 1'  # was '0 6 * * 1' — any non-:00 minute avoids the herd

Full guide: how to fix this →

No job timeout · Congratsbot

~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 · Diff Dependencies

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

Full-history clone (fetch-depth: 0) · Diff Dependencies

~0 min/mo

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 here

Full guide: how to fix this →

No job timeout · Format

~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 · Issue: Needs Repro

~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 · Label PRs

~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 · Release

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

Workflow can trigger itself · Release

~0 min/mo

Runs on push, pushes back with a custom token, and has no recursion guard, so this shape can trigger itself in a loop. Add `[skip ci]` to the commit, a `paths:` filter, or a `github.actor` gate.

      - run: |
          git commit -m "chore: update [skip ci]"
          git push

Full guide: how to fix this →

No job timeout · Semgrep OSS scan

~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 · Semgrep OSS scan

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

Scheduled at the top of the hour · Semgrep OSS scan

~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: '6 0 * * 6'  # was '0 0 * * 6' — any non-:00 minute avoids the herd

Full guide: how to fix this →

Scheduled workflow runs in forks · Semgrep OSS scan

~0 min/mo

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

Full guide: how to fix this →

No job timeout · Sync examples

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

No path filters on triggers · GitHub Actions Security Analysis with zizmor 🌈

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

Copy every fix as one block (12 snippets, annotated per workflow)
# Missing dependency cache (pnpm) (applies to: Release, Factory preview release)
- uses: actions/setup-node@v4
  with:
    node-version: 20
    cache: 'pnpm'

# No concurrency control (applies to: Examples astro check, Semgrep OSS scan, GitHub Actions Security Analysis with zizmor 🌈, Diff Dependencies, Check mergeability, Cleanup cache, Label PRs)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No job timeout (applies to: Check mergeability, Cleanup cache, Congratsbot, Diff Dependencies, Format, Issue: Needs Repro, Label PRs, Release, Semgrep OSS scan, Sync examples, GitHub Actions Security Analysis with zizmor 🌈)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Large build matrix (applies to: CI)
strategy:
  fail-fast: true
  matrix:
    include:
      - { os: ubuntu-latest, node: 20 }
      - { os: ubuntu-latest, node: 22 }

# Premium runners (macOS / Windows) (applies to: CI)
jobs:
  build:
    runs-on: ubuntu-latest  # ~10x cheaper than macos-latest

# Full-history clone (fetch-depth: 0) (applies to: CI, Diff Dependencies)
- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

# Scheduled at the top of the hour (applies to: Cleanup cache)
on:
  schedule:
    - cron: '20 11 * * *'  # was '0 11 * * *' — any non-:00 minute avoids the herd

# Scheduled at the top of the hour (applies to: PR: Close Duplicates)
on:
  schedule:
    - cron: '37 6 * * 1'  # was '0 6 * * 1' — any non-:00 minute avoids the herd

# Workflow can trigger itself (applies to: Release)
      - run: |
          git commit -m "chore: update [skip ci]"
          git push

# No path filters on triggers (applies to: Semgrep OSS scan, GitHub Actions Security Analysis with zizmor 🌈)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

# Scheduled at the top of the hour (applies to: Semgrep OSS scan)
on:
  schedule:
    - cron: '6 0 * * 6'  # was '0 0 * * 6' — any non-:00 minute avoids the herd

# Scheduled workflow runs in forks (applies to: Semgrep OSS scan)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

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

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/withastro/astro