You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should update our .golangci.yaml file to be more inline with upstream. It'll help make sure our package aliases are the same as the ones they use as well as enable better configs for things like gocritic which have caught at least one error in our code so far.
One discussion that I'd like to hear from others on is if we should keep the current strategy of only excluding problematic linters and otherwise including new linters golangci adds by default. Upstream instead only enables linters that they want/know work well. What do people want? Easiest thing to do is make it look as much as upstream as possible.
/kind feature
The text was updated successfully, but these errors were encountered:
cprivitere
added
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
and removed
kind/feature
Categorizes issue or PR as related to a new feature.
labels
Aug 7, 2023
We should update our .golangci.yaml file to be more inline with upstream. It'll help make sure our package aliases are the same as the ones they use as well as enable better configs for things like gocritic which have caught at least one error in our code so far.
One discussion that I'd like to hear from others on is if we should keep the current strategy of only excluding problematic linters and otherwise including new linters golangci adds by default. Upstream instead only enables linters that they want/know work well. What do people want? Easiest thing to do is make it look as much as upstream as possible.
/kind feature
The text was updated successfully, but these errors were encountered: