Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
No concurrency control · Close Missing Playground issues
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: trueNo concurrency control · Close invalid questions issues
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: trueAlso found: 6 more config fixes with negligible recoverable minutes: timeouts, retention, path filters
No job timeout · Close Missing Playground issues
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: 15Frequent scheduled runs · Close Missing Playground issues
A schedule cron fires >4x/hour, so scheduled runs cost minutes around the clock. Loosen the cadence.
on:
schedule:
- cron: '*/30 * * * *' # every 30 min instead of every minuteScheduled workflow runs in forks · Close Missing Playground issues
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 · Close invalid questions issues
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: 15Frequent scheduled runs · Close invalid questions issues
A schedule cron fires >4x/hour, so scheduled runs cost minutes around the clock. Loosen the cadence.
on:
schedule:
- cron: '*/30 * * * *' # every 30 min instead of every minuteScheduled workflow runs in forks · Close invalid questions issues
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 (4 snippets, annotated per workflow)
# No concurrency control (applies to: Close Missing Playground issues, Close invalid questions issues)
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# No job timeout (applies to: Close Missing Playground issues, Close invalid questions issues)
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15
# Frequent scheduled runs (applies to: Close Missing Playground issues, Close invalid questions issues)
on:
schedule:
- cron: '*/30 * * * *' # every 30 min instead of every minute
# Scheduled workflow runs in forks (applies to: Close Missing Playground issues, Close invalid questions issues)
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/go-gorm/gorm)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.