wryenmeek/knowledgebase 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.

56 min/mo
recoverable (~15% of CI time) · across 20 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 20 fixes, each with the exact YAML ↓
7.4%
failure rate, 30d · Above average
1h 10m
avg time to recover from a failure
🕸️ Reliability: Above averageFailure rate beats ~59% of the 19 repos GitSpider watches.
Since : findings 21 → 20 · recoverable ~74 → ~56 min/mo (detector updated between scans, so part of this change is ours, not the repo's)
26 workflows · 500 runs (16.7/day) · 385 CI-min (wall-clock) · ≈$2 at private-repo rates (30d)

Where the minutes go (30d)

CI-2 Analyst Read-Only Diagnostics~139 min · 78 runs
Jules Account Probe~76 min · 14 runs
Pre-commit hooks~54 min · 140 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Missing dependency cache · Jules Account Probe

~23 min/mo

Set `cache: 'pip'` on your `actions/setup-python` step, or add an `actions/cache@v4` step keyed on your requirements/lock file.

- uses: actions/setup-python@v5
  with:
    python-version: '3.12'
    cache: 'pip'

Full guide: how to fix this →

Workflow runs on both push and pull_request · Pre-commit hooks

~23 min/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 · Pre-commit hooks

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

Workflow runs on both push and pull_request · Copilot Setup Steps

~4 min/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 · Copilot Setup Steps

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

No path filters on triggers · CI-2 Analyst Read-Only Diagnostics

~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 path filters on triggers · Commit Scope Check

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

Missing dependency cache · Fleet Plan

~0 min/mo

Set `cache: 'pip'` on your `actions/setup-python` step, or add an `actions/cache@v4` step keyed on your requirements/lock file.

- uses: actions/setup-python@v5
  with:
    python-version: '3.12'
    cache: 'pip'

Full guide: how to fix this →

Scheduled at the top of the hour · Fleet Plan

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

Full guide: how to fix this →

Scheduled workflow runs in forks · Fleet Plan

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

Scheduled at the top of the hour · Fleet Submit PRs

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

Full guide: how to fix this →

Scheduled workflow runs in forks · Fleet Submit PRs

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

Scheduled at the top of the hour · GitHub Customizations Freshness

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

Full guide: how to fix this →

Scheduled at the top of the hour · Jules Account Probe

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

Full guide: how to fix this →

No concurrency control · Post-Merge Body-vs-Diff Audit

~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 path filters on triggers · Pre-commit hooks

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

Full-history clone (fetch-depth: 0) · Pre-commit hooks

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

Scheduled at the top of the hour · Sweep Stale Bot Branches

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

Full guide: how to fix this →

Scheduled workflow runs in forks · Sweep Stale Bot Branches

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

Full-history clone (fetch-depth: 0) · Sweep Stale Bot Branches

~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 (11 snippets, annotated per workflow)
# Missing dependency cache (pip) (applies to: Jules Account Probe, Fleet Plan)
- uses: actions/setup-python@v5
  with:
    python-version: '3.12'
    cache: 'pip'

# Workflow runs on both push and pull_request (applies to: Pre-commit hooks, Copilot Setup Steps)
on:
  push:
    branches: [main]
  pull_request:

# No concurrency control (applies to: Pre-commit hooks, Copilot Setup Steps, Post-Merge Body-vs-Diff Audit)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No path filters on triggers (applies to: CI-2 Analyst Read-Only Diagnostics, Commit Scope Check, Pre-commit hooks)
on:
  pull_request:
    paths:
      - 'src/**'
      - 'package.json'

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

# Scheduled workflow runs in forks (applies to: Fleet Plan, Fleet Submit PRs, Sweep Stale Bot Branches)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

# Scheduled at the top of the hour (applies to: Fleet Submit PRs)
on:
  schedule:
    - cron: '8 4 * * *'  # was '0 4 * * *' — any non-:00 minute avoids the herd

# Scheduled at the top of the hour (applies to: GitHub Customizations Freshness)
on:
  schedule:
    - cron: '13 4 * * 1'  # was '0 4 * * 1' — any non-:00 minute avoids the herd

# Scheduled at the top of the hour (applies to: Jules Account Probe)
on:
  schedule:
    - cron: '27 0,9,18 * * *'  # was '0 0,9,18 * * *' — any non-:00 minute avoids the herd

# Full-history clone (fetch-depth: 0) (applies to: Pre-commit hooks, Sweep Stale Bot Branches)
- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

# Scheduled at the top of the hour (applies to: Sweep Stale Bot Branches)
on:
  schedule:
    - cron: '38 2 * * *'  # was '0 2 * * *' — 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/wryenmeek/knowledgebase.svg)](https://gitspider.com/scan/wryenmeek/knowledgebase)

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.

Share this scorecard: https://gitspider.com/scan/wryenmeek/knowledgebase