chore: add golangci-lint config #107
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
This reverts commit a0e68b2.
Codecov Report
@@ Coverage Diff @@
## master #107 +/- ##
==========================================
- Coverage 96.21% 96.19% -0.02%
==========================================
Files 6 6
Lines 423 421 -2
==========================================
- Hits 407 405 -2
Misses 10 10
Partials 6 6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
evan-forbes
approved these changes
Feb 17, 2023
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.
While working on a different PR, my editor complained about failed go-staticcheck warnings. For consistency across codebases, I adopted the celestia-app golangci-lint config and fixed the lint errors in the screenshot below. This repo already has a lint workflow that runs golangci-lint so CI will run with these linters moving forward (confirmed via verbose logging here).
Screenshot