Skip to content
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

Feature request: Specifying version #70

Open
okuramasafumi opened this issue Aug 22, 2023 · 3 comments
Open

Feature request: Specifying version #70

okuramasafumi opened this issue Aug 22, 2023 · 3 comments

Comments

@okuramasafumi
Copy link
Contributor

Sometimes we'd like to specify the version of Codespell to control dictionaries. c.f. this commit in Rails.
Could we add the ability to specify the version of Codespell to install?

@akien-mga
Copy link

I'd like this too for https://github.com/godotengine/godot

The action seems to use the latest dictionary from https://github.com/codespell-project/codespell, and while that's nice, it means that we start getting PRs failing due to typos not introduced by these PRs. It's a bother to contributors, and particularly annoying for stable branches where we don't necessarily run codespell daily so bugfix updates also fail CI.

@mateusoliveira43
Copy link

I saw the problem of PRs failing due to typos not introduced by these PRs in a project I work (of course, because we use @master instead of a fixed version, but we would like to receive updates with more frequency).

One suggestion would be to create an automation that after a new release in https://github.com/codespell-project/codespell, a new release would be created here. This way, we can use dependabot PRs to update the action regularly, and fix the new typos within those PRs.

@skoudoro
Copy link

skoudoro commented Jul 1, 2024

+1 for this request.

and question, How do I use the latest release : codespell v2.3.0 ? Many new features available that we would like to use.

Thank you for your future feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants