Extra-Chill/homeboy GitHub Actions scorecard

Public GitHub Actions data, last 30 days. Updated 7/11/2026, 5:15:26 AM.

Data sourced from public GitHub. GitSpider is not affiliated with or endorsed by this repository's owners. Request removal.

0 min/mo
recoverable · across 5 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 5 fixes, each with the exact YAML ↓
10.0%
failure rate, 30d
29m
avg time to recover from a failure
3 workflows · 500 runs (16.7/day) · 10,807 CI-min (wall-clock) · ≈$65 at private-repo rates (30d)

Where the minutes go (30d)

Release~5,878 min · 256 runs
CI~4,929 min · 244 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

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 →

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 · 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 (3 snippets, annotated per workflow)
# No job timeout — applies to: CI, Release
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

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

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

Each snippet is representative — merge into the named workflow files rather than pasting wholesale.

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 →

Not ready to install? Get this report by email. No spam, unsubscribe anytime.

Share this scorecard: https://gitspider.com/scan/Extra-Chill/homeboy
Add the badge to your README

Live CI-health badge → GitSpider badge

[![GitSpider](https://gitspider.com/badge/Extra-Chill/homeboy.svg)](https://gitspider.com/scan/Extra-Chill/homeboy)