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
I run Bandit in CI for a few repos now, and it's been both useful when finding potential issues (and one actual problem - thanks!) and annoyingly verbose when everything is OK. I just don't want contributors to have to scroll through 27 lines of output when silence would be fine and the failure is coming from some other tool.
So in the Unix tradition of "silence is golden", I would love a --quiet and a --silent option to take output away, just as the existing --verbose and --debug options add more.
The text was updated successfully, but these errors were encountered:
This commit adds a new command line argument to hide output
when the result of the scan is passing with no warning/errors.
The new option is -q or --quiet. It also allows --silent to be
consistent with the GNU standard on CLI options [1].
[1] http://www.gnu.org/prep/standards/html_node/Option-Table.html#Option-Table
Signed-off-by: Eric Brown <browne@vmware.com>
Fixes Issue #384
I run Bandit in CI for a few repos now, and it's been both useful when finding potential issues (and one actual problem - thanks!) and annoyingly verbose when everything is OK. I just don't want contributors to have to scroll through 27 lines of output when silence would be fine and the failure is coming from some other tool.
So in the Unix tradition of "silence is golden", I would love a
--quiet
and a--silent
option to take output away, just as the existing--verbose
and--debug
options add more.The text was updated successfully, but these errors were encountered: