chore: only check new issues with Go linter #10054
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
3 tasks
powersj
pushed a commit
that referenced
this pull request
Nov 17, 2021
(cherry picked from commit 00325f2)
VladislavSenkevich
pushed a commit
to gwos/telegraf
that referenced
this pull request
Nov 23, 2021
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.
The official github action for golangci-lint has the option to only fail for newly introduced issues, this feature is missing for the github action super linter (this caused an issue for the PR: #10051). This pull request re-introduces the old github action config for golangci-lint, but keeps the super linter for only markdown.
Also removed the tag from the README because all it shows as failed if any PR fails a lint, so that seems useless.