exit-status-echo
A deny rule by default: it refuses a line ending by printing an exit status, which the harness already reports, and names what to run instead.
What it catches
A line ending by printing an exit status, which the harness already reports.
Why
The harness reports a nonzero exit on its own and success needs no confirmation, so cmd; echo "rc=$?" adds lines and no information. It also misreports: the echo exits 0, so the line as a whole passes whatever cmd did. Every spelling of that ending fires: echo/printf of $? with literal text, to the console or stderr; the same through a capture (rc=$?; echo $rc); cmd || echo "failed $?", where the echo runs exactly when cmd failed; and ${PIPESTATUS[...]}, whose answer is set -o pipefail or no pipe. exit $?, [ $? -ne 0 ], an echo mid-script, one after &&, and one redirected to a file keep the status for later logic and are untouched. Chain with &&, or make separate calls, when a failure must not be masked.
Default and override
By default this rule takes the decision deny. A workspace sets it by name, in its root
magusfile, to deny, advise or off:
magus\guard.builtins({"exit-status-echo": "advise"})
A loosening takes effect once it is committed; a tightening applies at once.
Seeing it
A verdict names its rule in brackets, which is how you got here:
deny [exit-status-echo]: ...
A workspace that sets this rule to advise sees advise [exit-status-echo]: ... instead.
magus describe rule exit-status-echo prints the same entry at a terminal, and
magus describe rules lists every rule this workspace enforces.
See also
- All rules - what this workspace enforces, deny first
- The guard - how a verdict is reached and wired
- Setting a built-in rule - how a workspace changes this default