Skip to content
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

lint: various fixes and improvements #119893

Merged
merged 1 commit into from
Mar 5, 2024

Conversation

rickystewart
Copy link
Collaborator

  1. Use code generation to remove the lint build tag for running lints.
    On the Bazel side, you're not likely to accidentally run these tests
    and build tags just slow things down.
  2. Fix the script for the nightly lint to exit with the correct status
    code and generate code before running.
  3. Fix some lint errors in lint_test.go itself.

Epic: none
Release note: None

@rickystewart rickystewart requested a review from rail March 4, 2024 22:37
@rickystewart rickystewart requested review from a team as code owners March 4, 2024 22:37
@rickystewart rickystewart requested review from DrewKimball and removed request for a team March 4, 2024 22:37
@cockroach-teamcity
Copy link
Member

This change is Reviewable

1. Use code generation to remove the `lint` build tag for running lints.
   On the Bazel side, you're not likely to accidentally run these tests
   and build tags just slow things down.
2. Fix the script for the nightly lint to exit with the correct status
   code and generate code before running.
3. Fix some lint errors in `lint_test.go` itself.

Epic: none
Release note: None
Copy link
Member

@rail rail left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, :shipit:

@rickystewart
Copy link
Collaborator Author

bors r=rail

@craig
Copy link
Contributor

craig bot commented Mar 5, 2024

Build succeeded:

@craig craig bot merged commit 3e61bd3 into cockroachdb:master Mar 5, 2024
17 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants