Open WilliamRoyNelson opened 3 months ago
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors.
To be clear, if there are compelling technical reasons to not make this change, don't feel like you need to break things. I'm mostly hoping that the only obstacle is "nobody ever asked and nobody thought to do it" which is an easy obstacle to overcome 😄
some corporate environments
I feel like corporates don't really care about golangci-lint maintainers: https://opencollective.com/golangci-lint#category-BUDGET
I use "main" for all my new projects, but the impacts are important for existing projects. In the context of golangci-lint, there are multiple internal and external references that I don't want to break. This doesn't mean we will never change, but this requires a lot of work and time.
Welcome
Your feature request related to a problem? Please describe
The name "main" is increasingly becoming the standard for default branch names, and it's in alignment with this project's Code of Conduct which requires the use of inclusive language.
The reason that this is important, as trivial as it may seem, is that in some corporate environments it can cause documentation or code to be flagged if it contains certain terms like "master" or "abort."
As a bonus, it saves two keystrokes! That's a 50% increase in efficiency if you look at it from a very contrived angle!
Describe the solution you'd like
GitHub has a guide on how to easily make this change: https://github.com/github/renaming
Describe alternatives you've considered
In documentation instead of using a link like: https://github.com/golangci/golangci-lint/blob/master/.golangci.reference.yml
I can instead use https://github.com/golangci/golangci-lint/blob/HEAD/.golangci.reference.yml
Additional context
No response
Supporter