Fix typos in the documentation - #16
Conversation
8ad93fa to
2624b6a
Compare
|
Thanks for spotting these with Since you used I’d be interested in what you think would be the most appropriate setup for this project, including how you would deal with project-specific words or false positives. |
|
@ifilot Yes, i think i can integrate that. I would say a warning on a build would help with it. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #16 +/- ##
==========================================
+ Coverage 77.58% 77.76% +0.18%
==========================================
Files 10 10
Lines 1111 1111
Branches 533 533
==========================================
+ Hits 862 864 +2
+ Misses 178 176 -2
Partials 71 71
🚀 New features to boost your workflow:
|
|
@goelakash Thanks! The workflow is running, but from the Actions log it looks like the new Could you update the workflow so the action explicitly uses the repository config/ignore file? It might also be useful to save the codespell output as a workflow artifact (for example, a |
|
Done both. One thing though: the config was already being used. codespell reads Passing it explicitly anyway since it is clearer, and added the Example run, with three typos I added on purpose so there is something to see: |
Fixes 2 spelling mistakes in the docs, found with
codespell.Prose only. No code identifiers, module paths, package names or proper nouns changed, and anything that was a valid alternative spelling rather than a misspelling was left alone.