← ClaudeAtlas

local_cilisted

Diagnose a GitHub Actions billing/minutes lockout and move CI to a self-hosted runner — the escape hatch when a private repo runs out of free minutes
VytCepas/project-init · ★ 0 · DevOps & Infrastructure · score 69
Install: claude install-skill VytCepas/project-init
# Local CI — when GitHub Actions minutes run out On a **private** repo that exhausts its Actions minutes (or hits a spending-limit/payment problem), every job fails at start and the required checks never report — the merge gate stalls. Verification itself never stops (see step 2); only the remote checks do. ## 1. Diagnose — confirm it's the billing lockout ```bash gh run list --limit 5 --json conclusion,displayTitle ``` The lockout signature is `startup_failure` with the annotation *"The job was not started because recent account payments have failed or your spending limit needs to be increased."* Check remaining minutes: ```bash # Enhanced billing platform (current; filter for Actions usage): gh api "/users/{username}/settings/billing/usage" --jq '[.usageItems[] | select(.product == "actions")]' gh api "/organizations/{org}/settings/billing/usage" --jq '[.usageItems[] | select(.product == "actions")]' # Accounts not yet on the enhanced platform: the legacy endpoint still answers: gh api /users/{username}/settings/billing/actions ``` If runs are failing for any *other* reason, this skill does not apply — fix the actual failure. ## 2. Immediate unblock — the gate already runs locally `just ci` runs the **same recipes CI runs** (the justfile is the single command surface), and the pre-push git hook already enforces it on every push. Nothing about correctness is blocked — keep working; only the merge gate needs the fix below. ## 3. Durable fix — self-hosted runner (zero