Skip to content

Fix typo, check in CI going forward #71

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

Closed

Conversation

waywardmonkeys
Copy link
Contributor

This pins a version of the typos check which means someone would need to periodically update it. That prevents people from having to fix typos unrelated to their changes, should there be new things found by a future update of the typos check.

This pins a version of the typos check which means someone would
need to periodically update it. That prevents people from having
to fix typos unrelated to their changes, should there be new
things found by a future update of the typos check.
[files]
# Include .github, .cargo, etc.
ignore-hidden = false
extend-exclude = [
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should probably include src/code.rs and src/named_key.rs, since those are auto-generated and mostly outside our control.

Comment on lines +19 to +21
# /.git isn't in .gitignore, because git never tracks it.
# Typos doesn't know that, though.
"/.git",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds like a bug in typos? Do you know if there is one?

@madsmtm
Copy link
Member

madsmtm commented Mar 27, 2025

Looks fine to me (with comments resolved)

@pyfisch
Copy link
Contributor

pyfisch commented Apr 21, 2025

I fixed the typo in main. However I think it is not necessary to check for typos continuously and incur the maintenance overhead for another CI job

@pyfisch pyfisch closed this Apr 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants