GitSpider

chapati/sky-blue-bootc 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.

0 min/mo
recoverable · across 2 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 2 fixes, each with the exact YAML ↓
44.7%
failure rate, 30d
28h 24m
avg time to recover from a failure
3 workflows · 76 runs (2.5/day) · 376 CI-min (wall-clock) · ≈$2 at private-repo rates (30d)

Where the minutes go (30d)

Build container image~374 min · 74 runs
Dependabot Updates~3 min · 2 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No job timeout · Build container image

~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 · Build container image

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

Full guide: how to fix this →

Copy every fix as one block (2 snippets, annotated per workflow)
# No job timeout (applies to: Build container image)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Scheduled at the top of the hour (applies to: Build container image)
on:
  schedule:
    - cron: '20 07 * * SAT'  # was '00 07 * * SAT' — 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/chapati/sky-blue-bootc.svg)](https://gitspider.com/scan/chapati/sky-blue-bootc)

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/chapati/sky-blue-bootc