pytest-dev/pytest 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 · across 12 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 12 fixes, each with the exact YAML ↓
14.7%
failure rate, 30d
2h 17m
avg time to recover from a failure
Since : findings 6 → 12 · recoverable ~1 → ~1 min/mo
13 workflows · 456 runs (15.2/day) · 5,470 CI-min (wall-clock) · ≈$33 at private-repo rates (30d)

Where the minutes go (30d)

test~5,339 min · 386 runs
Doc Check Links~76 min · 5 runs
Dependabot Updates~29 min · 23 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · close needs-information issues

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

No job timeout · Doc Check Links

~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 · Doc Check Links

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

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · Doc Check Links

~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 · close needs-information 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 →

Scheduled workflow runs in forks · close needs-information issues

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

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

Large build matrix · test

~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) · test

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

No job timeout · Update Plugin List

~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 · Update Plugin List

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

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · Update Plugin List

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

Copy every fix as one block (9 snippets, annotated per workflow)
# No concurrency control (applies to: close needs-information issues)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No job timeout (applies to: Doc Check Links, close needs-information issues, Update Plugin List)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Scheduled at the top of the hour (applies to: Doc Check Links)
on:
  schedule:
    - cron: '32 0 * * 0'  # was '0 0 * * 0' — any non-:00 minute avoids the herd

# Full-history clone (fetch-depth: 0) (applies to: Doc Check Links, Update Plugin List)
- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

# Scheduled workflow runs in forks (applies to: close needs-information issues)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

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

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

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

# Scheduled at the top of the hour (applies to: Update Plugin List)
on:
  schedule:
    - cron: '54 0 * * 0'  # was '0 0 * * 0' — any non-:00 minute avoids the herd

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

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/pytest-dev/pytest