Where the minutes go (30d)
Waste detected
Biggest wins first, each with the exact config fix.
Workflow runs on both push and pull_request · ci
Pushing to a branch and opening a PR triggers two runs. Pick one (usually `pull_request`) and exclude branch pushes for non-default branches.
on:
push:
branches: [main]
pull_request:No concurrency control · ci
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: 1 more config fix with negligible recoverable minutes — timeouts, retention, path filters
No job timeout · ci
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 (3 snippets, annotated per workflow)
# Workflow runs on both push and pull_request — applies to: ci
on:
push:
branches: [main]
pull_request:
# No concurrency control — applies to: ci
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
# No job timeout — applies to: ci
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15Each 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.
Live CI-health badge → 
[](https://gitspider.com/scan/hipvlady/agent-coherence-plugin)