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
running bazel lint / aspect lint produces an exit code that governs how callers (like a CI script) will interpret whether the developer should be blocked. However unless your shell is setup to echo exit codes, this isn't visible.
Describe the feature
Print overall status like ":heavy_white_check: Lint Passed" or ":siren: Lint Failed" at the end of the stdout following the last report.
(note to Aspect: this is requested by a prospective customer)
The text was updated successfully, but these errors were encountered:
I think the distinction is that it's nice to run bazel lint //... on every target whereas the docs outline running it on a sub-package.
Running it on the whole repo prints out a lot obviously as it goes through every package.
I would suspect most people are not interested in the success case and only the failures.
What is the current behavior?
running
bazel lint
/aspect lint
produces an exit code that governs how callers (like a CI script) will interpret whether the developer should be blocked. However unless your shell is setup to echo exit codes, this isn't visible.Describe the feature
Print overall status like ":heavy_white_check: Lint Passed" or ":siren: Lint Failed" at the end of the stdout following the last report.
(note to Aspect: this is requested by a prospective customer)
The text was updated successfully, but these errors were encountered: