Repository navigation
Commit 4ed44eb
committed
docs(release): use the built binary where the audit's exit code matters
The README said `go run` forwards the audit's exit code. It does not:
any non-zero exit of the program comes back as go run's own 1, after an
"exit status N" line on stderr. An audit that could not be completed
exits 2 precisely so a gate can tell "no answer" from "outstanding
work", and under go run the two look identical -- `--limit 0` exits 2
from the binary and 1 from go run.
Show the exit-code example with the built binary, branching on all
three codes, and say that go run is fine for reading the report but not
for anything that acts on the exit status. /backport-audit is already
in .gitignore, so building it at the repository root leaves nothing to
commit by accident.
Assisted-by: LLM
Signed-off-by: Myasnikov Daniil <[email protected]>1 parent a6c3772 commit 4ed44eb
1 file changed
Lines changed: 8 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
42 | 42 | | |
43 | 43 | | |
44 | 44 | | |
45 | | - | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
46 | 52 | | |
47 | 53 | | |
48 | | - | |
| 54 | + | |
49 | 55 | | |
50 | 56 | | |
51 | 57 | | |
| |||
0 commit comments