-
Notifications
You must be signed in to change notification settings - Fork 533
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
draft: Add codespell CI job and fix some typos #3501
Conversation
17f837b
to
fe8c438
Compare
Assuming its not long for this mortal world (?). Also check locales for now.
Too many false positive from non-English for example.
@JorjMcKie Do you know what "parm angle" means here? does it mean "reduce angle parameter by"?
edit: I went ahead and removed that comment, seems a little WET anyway. |
It fails confusingly if you don't have a newline at the end of a file, and since not everyone's editor does that automatically, let's leave a comment for end of file.
Only two more errors where I'm uncertain what change to make (see above). After we make those, this is ready to go! If you like feel free to move the job to some other .yaml file. |
Did I break this test somehow?
|
Thanks for this PR, i hadn't come across codespell before, and it looks to be doing some very useful checking here. I think there's a trivial indentation error in the patch that's causing the test failure. I think we should run codespell as part of the existing pytest test suite, alongside pylint and flake8, rather than only has a Github action. I can make that change but alternatively feel free to add a new file |
Thanks @julian-smith-artifex-com I think I've done those changes but the test is still failing :(
Is it clear to you what that change was? thanks! |
Would you like this rebased and some of my small testing commits squashed into cleaner commits? |
There's an error message from test_quick:
So init.py", line 11304 is indented incorrectly in your branch i think? |
Apologies for taking a while to look at this again. Things that need updating:
I'd be happy to do some/all of these (preserving your name in the commits) if that's easier, but equally happy for you to do things. Thanks. |
I've taken the liberty of extracting your commit with the new codespell test into a new PR #3656. This has a smaller set of fixes, with a view to getting a PR for codespell (codespell-project/codespell#3476) accepted which will allow us to mark multiline regions of input files to be excluded from codespell checking. |
thanks and sorry for not getting back to you with revisions. Happy to see it merged. |
codespell
actionpossibly set it to warn only instead of errorBasic idea here is to run
codespell
on all merge requests. There are two files to place exceptions in, but in my experience these are rare and it generally does a good job, fixing more things than the hassle of the occasional exception.I have excluded the
tests/
dir b/c there are lots of false positives there (mostly b/c of non-English text). It should be fairly self explanatory how to exclude other directories in the future if you need.