-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add a CI for detecting typos #188
Comments
Ok, why not! Can you add it in the Makefile too? Thanks! |
@EwenQuim @ccoVeille Can you please review and approve the PR here - #189? |
This one has been addressed with #189. This one can be closed! |
Misspell is fine, I planned to add it too. So thank you! but unfortunately it is not enough for documenation in Markdown files. Please let this issue open, I'll open a PR soon |
ccoVeille
added a commit
to ccoveille-forks/go-fuego
that referenced
this issue
Sep 4, 2024
This checker won't detect all typos, but will report the obvious ones. It's a matter of balance. Too much typos, leads to false-positive. false-positive leads to maintain a list of exception, quite a pain. Fixes go-fuego#188
ccoVeille
added a commit
to ccoveille-forks/go-fuego
that referenced
this issue
Sep 4, 2024
This checker won't detect all typos, but will report the obvious ones. It's a matter of balance. Too much typos, leads to false-positive. false-positive leads to maintain a list of exception, quite a pain. Fixes go-fuego#188
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following #187, may I suggest to set up a CI for catching obvious typos?
I did it on many repository, I can help.
I would suggest a linter that has almost no false positive
The text was updated successfully, but these errors were encountered: