Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
No path filters on triggers · CI
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'Scheduled at the top of the hour · CI
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: '35 0 * * MON' # was '0 0 * * MON' — any non-:00 minute avoids the herdScheduled workflow runs in forks · CI
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-latestNo job timeout · deploy-binder
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: 15Copy every fix as one block (4 snippets, annotated per workflow)
# No path filters on triggers (applies to: CI)
on:
pull_request:
paths:
- 'src/**'
- 'package.json'
# Scheduled at the top of the hour (applies to: CI)
on:
schedule:
- cron: '35 0 * * MON' # was '0 0 * * MON' — any non-:00 minute avoids the herd
# Scheduled workflow runs in forks (applies to: CI)
jobs:
nightly:
if: github.repository == 'owner/repo'
runs-on: ubuntu-latest
# No job timeout (applies to: deploy-binder)
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15Each snippet is representative. Merge into the named workflow files rather than pasting wholesale.
Live CI-health badge → 
[](https://gitspider.com/scan/punch-mission/punchbowl)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.