Skip to content

Allow alternative to codespell in sp-repo-review #459

Description

@burgholzer

PC160 currently suggests the use of codespell in pre-commit.
However, codespell can be quite slow at times and can easily miss certain typos.
While looking for alternatives, I stumbled upon the crate-ci/typos repository that is also used by ruff in favor of codespell.
The tool has quite an easy config scheme, is drastically faster, and also provides auto-fix support. Furthermore, it caught at least some additional typos that were not spotted by codespell when we introduced the new tool for our framework (munich-quantum-toolkit/core#625).

Right now, the use of the crate-ci/typos in favor of codespell requires us to ignore "PC160".

Would it make sense to expand the scope of the rule a little bit to something like "Uses a spellchecker" and allow for codespell and/or crate-ci/typos to be used?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions