DJ420-gif/PromptPulse 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 (~3% of CI time) · across 4 patterns
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 4 fixes, each with the exact YAML ↓
0.0%
failure rate, 30d
11 workflows · 77 runs (2.6/day) · 39 CI-min (wall-clock) · ≈$0 at private-repo rates (30d)

Where the minutes go (30d)

pages-build-deployment~15 min · 30 runs
🔗 Broken Link Checker~12 min · 4 runs
📈 AI Trend Monitor — Daily Report~9 min · 30 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

No concurrency control · 📈 AI Trend Monitor — Daily Report

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

No job timeout · 📈 AI Trend Monitor — Daily Report

~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 · 📈 AI Trend Monitor — Daily Report

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

Full guide: how to fix this →

Scheduled workflow runs in forks · 📈 AI Trend Monitor — Daily Report

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

Copy every fix as one block (4 snippets, annotated per workflow)
# No concurrency control — applies to: 📈 AI Trend Monitor — Daily Report
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

# No job timeout — applies to: 📈 AI Trend Monitor — Daily Report
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Scheduled at the top of the hour — applies to: 📈 AI Trend Monitor — Daily Report
on:
  schedule:
    - cron: '50 7 * * *'  # was '0 7 * * *' — any non-:00 minute avoids the herd

# Scheduled workflow runs in forks — applies to: 📈 AI Trend Monitor — Daily Report
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

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/DJ420-gif/PromptPulse
Add the badge to your README

Live CI-health badge → GitSpider badge

[![GitSpider](https://gitspider.com/badge/DJ420-gif/PromptPulse.svg)](https://gitspider.com/scan/DJ420-gif/PromptPulse)