-
Notifications
You must be signed in to change notification settings - Fork 7
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
ci: add typo checking #30
Conversation
PS: If you find this useful, I can PR this across the Cc @apoelstra. |
utACK 81bbee2. I'm a bit confused about how this works and distinguishes between bech32/base64/base58/hex words and "real" words. But in general I think it's a good idea and we should have some sort of automatic typo checking. Would also be happy to have this elsewhere in the rust-bitcoin ecosystem. |
81bbee2
to
9cc833b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 9cc833b
Awesome, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is sweet, thanks.
ACK 9cc833b
nit: There is a newline missing from the workflow. In case its interesting to you I have my editor configured to add a newline at end of file on save if its missing.
9cc833b
to
ac5fc0e
Compare
Done! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK ac5fc0e
Needs rebase mate. |
feb57cc
to
0d2848a
Compare
It looks like now there is a merge commit and an unsigned commit :). Can you try rebasing again. |
ad9356d
to
6ac14be
Compare
Still not quite right :) I pulled it down and had a look, I think you want to hard reset away the last patch and then rebase on master and fix the two conflicts. You should be left with a single patch. |
4197b67
to
6968fbf
Compare
Sorry, I was with a unsynced fork. Took me a while to figure out that this was the issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK 6968fbf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 6968fbf
Since this is a public-facing documentation/resource repository,
we should be extra-careful and
judicious with typos.
typos
is a powerful source code spell checker.I've added a CI job that runs on every PR and push to
master
(but can also be run manually withworkflow_dispatch
) that checks for typos.I've also added a config file
.typos.toml
that deals with false positives and ignore some vendor related files and some filetypes that we don't want to check/correct for typos,e.g. lock files.
Finally, I've also corrected a few typos that were in the codebase that typos flagged.
If you want to run yourself you can do a cargo install (or binstall) the typos-cli:
It is also available in several pkg managers,
check the installation options at the
typos
repo