Will It Vibe?continue-on-error hides step failures
Part of Testing & CI, which counts for 10% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A job or step sets continue-on-error: true, so its failure is swallowed and the workflow is still reported green. Real regressions can then merge unnoticed. This is a heuristic; it is sometimes intentional for advisory steps.
Why it matters
continue-on-error: true makes a failing job or step report success, so the workflow stays green even when that part failed. Real regressions can merge unnoticed and required checks can pass when they should not. This is a heuristic; the flag is legitimate for genuinely advisory steps, but it is often left on by accident.
How to fix it
Remove continue-on-error from steps whose failure should block. If a step is truly advisory (an optional linter, a flaky notification), keep the flag but surface the result some other way, for example by checking steps.<id>.outcome in a later summary step so the failure is at least visible.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo