-
-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maintained version of misspell #2823
Comments
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the |
Still outstanding |
@girlpunk the repo is still a fork, usually a hard-fork cuts links with the origin repo and announces it, do you think it would be possible that golang do that ? |
I'm not sure unfortunately, beyond making use of it I don't have any relation with the fork. |
@girlpunk if you post an issue there they might confirm what I need ? :) |
Looks like they do intend to |
Hello, As you are using golangci-lint you are using already using our fork of misspell 😄 Hard forks are rare (at least on GitHub), we don't need to do that and it's weird regarding the original author. |
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the |
Is your feature request related to a problem? Please describe.
Misspell was previously removed as the original version, by client9, is not maintained. However, misspell provides a significantly better spelling check for code (such as variable names, etc) than any other linter offered by megalinter.
Describe the solution you'd like
Golang are maintaining a fork of misspell at golangci/misspell. As such, I would like to suggest re-introducing misspell but from this fork rather than the original.
Describe alternatives you've considered
None
Additional context
None
The text was updated successfully, but these errors were encountered: