-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Build
If our bazel linter check fails in evergreen, the logs to not make it obvious what to do to fix the issues or how to run the linter. We should make the logs print something that is easy for developers to find and tells them how to fix the issues (run the linter with fix-all).