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

Fix several typos #6224

Merged
merged 2 commits into from
Jan 4, 2023
Merged

Fix several typos #6224

merged 2 commits into from
Jan 4, 2023

Conversation

jdufresne
Copy link
Contributor

No description provided.

@welcome
Copy link

welcome bot commented Jan 1, 2023

Thanks for opening a pull request and helping make RubyGems and Bundler better! Someone from the RubyGems team will take a look at your pull request shortly and leave any feedback. Please make sure that your pull request has tests for any changes or added functionality.

We use GitHub Actions to test and make sure your change works functionally and uses acceptable conventions, you can review the current progress of GitHub Actions in the PR status window below.

If you have any questions or concerns that you wish to ask, feel free to leave a comment in this PR or join our #rubygems or #bundler channel on Slack.

For more information about contributing to the RubyGems project feel free to review our CONTRIBUTING guide

Copy link
Member

@deivid-rodriguez deivid-rodriguez left a comment

Choose a reason for hiding this comment

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

Thanks!

Can you contribute fixes to bundler/lib/bundler/vendor/thor/ files to the upstream repository?

Also, how did you find all these? We used to have a spell checker in CI, but it never found any issues and I removed it.

@jdufresne
Copy link
Contributor Author

Can you contribute fixes to bundler/lib/bundler/vendor/thor/ files to the upstream repository?

Yup! I'll work on moving those upstream.

I have removed them from the PR here so this only includes non-vendored files.

Also, how did you find all these? We used to have a spell checker in CI, but it never found any issues and I removed it.

I used codespell. I believe Rails also uses this tool.

@jdufresne
Copy link
Contributor Author

Thor PR opened at:
rails/thor#806

@simi
Copy link
Member

simi commented Jan 2, 2023

@deivid-rodriguez
Copy link
Member

Definitely!

For what it's worth, we did have spell checking in CI for about a year, but I removed it because the one time the CI check showed as failed, it was because the action failed to install, not because of detecting any typos.

This one seems very easy to setup: https://github.com/codespell-project/actions-codespell. We could try if it detects a fair amount of the typos being fixed here.

@jdufresne
Copy link
Contributor Author

I went ahead and added a GitHub actions for codespell. This should catch future misspellings.

filetest
fo
hax
msdos
Copy link
Member

Choose a reason for hiding this comment

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

🧓 :)

.github/workflows/spell.yml Outdated Show resolved Hide resolved
Copy link
Member

@deivid-rodriguez deivid-rodriguez left a comment

Choose a reason for hiding this comment

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

Thanks so much, this is great!

@deivid-rodriguez deivid-rodriguez merged commit 2ae2926 into rubygems:master Jan 4, 2023
deivid-rodriguez added a commit that referenced this pull request Jan 6, 2023
Fix several typos

(cherry picked from commit 2ae2926)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants