You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Use a distinct exit code when a run stops at --max-cost #48
(Split out of #32.) CI can't currently tell "findings over --fail-on" apart from "stopped at the cost ceiling". Add a dedicated exit code for budget exceeded, document it next to --max-cost in docs/REFERENCE.md, and add a CLI test.
Where to look:src/secfoo/cli.py (run), src/secfoo/cost.py.
I'll take this one (distinct exit code when a run stops at --max-cost). Will keep it to the exit-code change plus tests and a short docs note, and open a PR referencing this issue.
Activity
dbdefault commentedon Nov 10, 2026
I'll take this one (distinct exit code when a run stops at
--max-cost). Will keep it to the exit-code change plus tests and a short docs note, and open a PR referencing this issue.