bump golangci-lint to v1.54 #619
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @Iceber, DetailsInstructions for interacting with me using comments are available here. |
Iceber
force-pushed
the
fix_golangci_lint
branch
2 times, most recently
from
0e92e1e
to
40b046a
Compare
Iceber
force-pushed
the
fix_golangci_lint
branch
from
40b046a
to
6ae4258
Compare
Signed-off-by: Iceber Gu <[email protected]>
Iceber
force-pushed
the
fix_golangci_lint
branch
from
6ae4258
to
b5dc43e
Compare
Iceber
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
https://github.com/clusterpedia-io/clusterpedia/actions/runs/7271599601/job/19812409857
Fix strange bug with golangci-lint action. Fixed after version upgrade from
v1.53.3tov1.54./kind bug
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: