-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*: enable nogo to use fast incremental linter #35344
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/9ff0d009646da877e0a2f629723e37c76fbee05a |
9a35333
to
ca261a9
Compare
/run-build |
/run-build |
/run-unit-test |
6271b25
to
4be565b
Compare
Signed-off-by: Weizhen Wang <[email protected]>
/run-all-tests |
/run-all-tests |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 955b4d0
|
/run-unit-test |
/run-mysql-test |
What problem does this PR solve?
Issue Number: ref #35345
Problem Summary:
What is changed and how it works?
We spend too much time on the linter. we can use a fast incremental linter by enabling nogo to save time. It uses bazel's remote cache to check the code linter when the code has been changed.
First we use Bazel nogo to replace with govet
Check List
Tests
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.