Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
Workflow failing almost every run · Aggregate MCP Registry
Fails or times out on nearly all recent runs, burning minutes to produce only red, and an always-red workflow usually gets ignored. Fix it, or disable the trigger until it's ready.
Also found: 3 more config fixes with negligible recoverable minutes — timeouts, retention, path filters
No job timeout · Aggregate MCP Registry
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: 15Scheduled at the top of the hour · Aggregate MCP Registry
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: '52 * * * *' # was '0 * * * *' — any non-:00 minute avoids the herdScheduled workflow runs in forks · Aggregate MCP Registry
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-latestCopy every fix as one block (3 snippets, annotated per workflow)
# No job timeout — applies to: Aggregate MCP Registry
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15
# Scheduled at the top of the hour — applies to: Aggregate MCP Registry
on:
schedule:
- cron: '52 * * * *' # was '0 * * * *' — any non-:00 minute avoids the herd
# Scheduled workflow runs in forks — applies to: Aggregate MCP Registry
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latestEach snippet is representative — merge into the named workflow files rather than pasting wholesale.
Live CI-health badge → 
[](https://gitspider.com/scan/CrimsonXover/qt-creator)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.