Skip to content

feat: migrate to use typos#180

Merged
jiacai2050 merged 1 commit intomainfrom
migrate-to-typos
Feb 11, 2026
Merged

feat: migrate to use typos#180
jiacai2050 merged 1 commit intomainfrom
migrate-to-typos

Conversation

@chenrui333
Copy link
Contributor

seeing some misspell false report in https://github.com/zigcc/awesome-zig/runs/63190590006, thus migrate to use typos (which is more well maintained)

"chilli" is a misspelling of "chili"

seeing some misspell false report

```
"chilli" is a misspelling of "chili"
```

Signed-off-by: Rui Chen <rui@chenrui.dev>
@gemini-code-assist
Copy link

Summary of Changes

Hello @chenrui333, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request improves the accuracy of the project's documentation by correcting a reported misspelling in the README.md file. The change addresses a specific typo and aligns with the author's stated goal of migrating to the typos tool to enhance overall spell-checking and prevent future inaccuracies.

Highlights

  • Spelling Correction: Corrected a misspelling of "mechanizm" to "mechanism" within the README.md file, specifically in the description of the g41797/mailbox project under the Multithreading section.
  • Tool Migration Intent: The pull request description indicates an intention to migrate to the typos tool to address false positive spell-check reports, aiming for more accurate and reliable spell-checking.
Changelog
  • README.md
    • Corrected a typo from "mechanizm" to "mechanism" in the description of the g41797/mailbox project.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/typos.yml
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request corrects a spelling error in README.md, changing 'mechanizm' to 'mechanism'. The change is correct and improves the documentation. No other issues were found in the diff.

@jiacai2050 jiacai2050 merged commit 3622597 into main Feb 11, 2026
2 checks passed
@jiacai2050 jiacai2050 deleted the migrate-to-typos branch February 11, 2026 22:45
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

Successfully merging this pull request may close these issues.

2 participants