GitSpider

mrpilot2/aide GitHub Actions scorecard

Public GitHub Actions data, last 30 days. Updated .

Data sourced from public GitHub. GitSpider is not affiliated with or endorsed by this repository's owners. Request removal.

174 min/mo
recoverable (~15% of CI time) · across 6 patterns · ≈$1/mo
Estimated from wall-clock time · public repos pay $0, $ = private-repo equivalent
See all 6 fixes, each with the exact YAML ↓
14.6%
failure rate, 30d
5h 15m
avg time to recover from a failure
Since : findings 6 → 6 · recoverable ~173 → ~174 min/mo
16 workflows · 41 runs (1.4/day) · 1,180 CI-min (wall-clock) · ≈$7 at private-repo rates (30d)

Where the minutes go (30d)

CI - Main~871 min · 25 runs
CodeQL~208 min · 12 runs
CI - Weekly~101 min · 4 runs
or track on every push →

Waste detected

Biggest wins first, each with the exact config fix.

Workflow runs on both push and pull_request · CI - Main

~174 min/mo · ≈$1/mo

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:

Full guide: how to fix this →

Also found: 5 more config fixes with negligible recoverable minutes: timeouts, retention, path filters

No job timeout · CI - Main

~0 min/mo

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: 15

Full guide: how to fix this →

No job timeout · CodeQL

~0 min/mo

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: 15

Full guide: how to fix this →

Scheduled workflow runs in forks · CodeQL

~0 min/mo

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-latest

Full guide: how to fix this →

Full-history clone (fetch-depth: 0) · CodeQL

~0 min/mo

checkout fetches the entire git history every run (`fetch-depth: 0`) and nothing in the workflow appears to read it. Remove the line; the default shallow clone is much faster on big repos. Keep it if a step genuinely needs history.

- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

Full guide: how to fix this →

System packages reinstalled every run · CodeQL

~0 min/mo

System packages install from the network on every run with no cache. Cache them (cache-apt-pkgs-action) or check whether the runner image already has the tool.

- uses: awalsh128/cache-apt-pkgs-action@latest
  with:
    packages: <your packages>
    version: 1.0

Full guide: how to fix this →

Copy every fix as one block (5 snippets, annotated per workflow)
# Workflow runs on both push and pull_request (applies to: CI - Main)
on:
  push:
    branches: [main]
  pull_request:

# No job timeout (applies to: CI - Main, CodeQL)
jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 15

# Scheduled workflow runs in forks (applies to: CodeQL)
jobs:
  nightly:
    if: github.repository == 'owner/repo'
    runs-on: ubuntu-latest

# Full-history clone (fetch-depth: 0) (applies to: CodeQL)
- uses: actions/checkout@v4
  # fetch-depth: 0 removed — default shallow clone is enough here

# System packages reinstalled every run (applies to: CodeQL)
- uses: awalsh128/cache-apt-pkgs-action@latest
  with:
    packages: <your packages>
    version: 1.0

Each snippet is representative. Merge into the named workflow files rather than pasting wholesale.

Add the badge to your README

Live CI-health badge → GitSpider badge

[![GitSpider](https://gitspider.com/badge/mrpilot2/aide.svg)](https://gitspider.com/scan/mrpilot2/aide)

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.

Share this scorecard: https://gitspider.com/scan/mrpilot2/aide