Make linting/formatting errors more obvious in CI
Open
minor enhancement
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 302
- PR merge metrics
- No merged PRs in 30d
Description
I think it's not so easy to figure out what has gone wrong in presubmit in CI. I've gotten two separate complaints about this.
To make it clearer:
1. We should print the string "error" near where the error occurs so it can be searched for.
2. We should remove noise from the presubmit run. In particular this complaint from pip confuses people: ```"ERROR: google-api-core 1.17.0 has requirement google-auth<2.0dev,>=1.14.0, but you'll have google-auth 1.11.0 which is incompatible.``` so we should fix it or maybe even do pip stuff in another step so people don't even have to see it.
Contributor guide
Assessment
This issue has not been assessed yet.