AndreLiar/Retrieva 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.

32 min/mo
recoverable (~8% of CI time) · across 12 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 12 fixes, each with the exact YAML ↓
29.8%
failure rate, 30d
1h 54m
avg time to recover from a failure
Since : findings 0 → 12 · recoverable ~0 → ~32 min/mo
5 workflows · 161 runs (5.4/day) · 396 CI-min (wall-clock) · ≈$2 at private-repo rates (30d)

Where the minutes go (30d)

CI~142 min · 62 runs
Release~91 min · 47 runs
Build~91 min · 23 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · CI

~14 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 · Build

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

~9 min/mo

Add a `concurrency:` block keyed on branch to cancel superseded runs when devs push twice quickly.

concurrency:
  group: ${{ github.workflow }}
  # no cancel-in-progress on deploys: queued deploys would be dropped

Full guide: how to fix this →

Also found: 9 more config fixes with negligible recoverable minutes: timeouts, retention, path filters

No job timeout · BMAD Sync

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

Third-party actions pinned to a mutable ref · BMAD Sync

~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: andrelair-platform/.github/.github/workflows/bmad-sync.yml@<full-sha>  # was @main

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 job timeout · CI

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

~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 · Deploy Docs

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

cancel-in-progress on a deploy workflow · Deploy Docs

~0 min/mo

This looks like a deploy/release workflow with `cancel-in-progress: true`, which cancels queued runs too, so a queued deploy is silently dropped when a newer run arrives. Use a group-only `concurrency:` block on deploys.

concurrency:
  group: ${{ github.workflow }}
  # queued deploys run in order; none are dropped

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 →

No path filters on triggers · Release

~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 (6 snippets, annotated per workflow)
# No concurrency control (applies to: CI, Build)
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No concurrency control (applies to: Release)
concurrency:
  group: ${{ github.workflow }}
  # no cancel-in-progress on deploys: queued deploys would be dropped

# No job timeout (applies to: BMAD Sync, Build, CI, Deploy Docs, Release)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Third-party actions pinned to a mutable ref (applies to: BMAD Sync)
uses: andrelair-platform/.github/.github/workflows/bmad-sync.yml@<full-sha>  # was @main

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

# cancel-in-progress on a deploy workflow (applies to: Deploy Docs)
concurrency:
  group: ${{ github.workflow }}
  # queued deploys run in order; none are dropped

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

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/AndreLiar/Retrieva