Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
Large build matrix · CI (Nightly)
The matrix expands to many parallel jobs per run, multiplying billable minutes, often more combos than you need. Trim the axes, or use `include:` to list only the combinations that matter.
strategy:
fail-fast: true
matrix:
include:
- { os: ubuntu-latest, node: 20 }
- { os: ubuntu-latest, node: 22 }Scheduled at the top of the hour · CI (Nightly)
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: '53 3 * * *' # was '0 3 * * *' — any non-:00 minute avoids the herdScheduled workflow runs in forks · CI (Nightly)
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)
# Large build matrix (applies to: CI (Nightly))
strategy:
fail-fast: true
matrix:
include:
- { os: ubuntu-latest, node: 20 }
- { os: ubuntu-latest, node: 22 }
# Scheduled at the top of the hour (applies to: CI (Nightly))
on:
schedule:
- cron: '53 3 * * *' # was '0 3 * * *' — any non-:00 minute avoids the herd
# Scheduled workflow runs in forks (applies to: CI (Nightly))
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/EffortlessMetrics/perl-lsp-swarm)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.