Skip to content

Chore/add codespell ignore words - #212

Merged
NiveditJain merged 4 commits into
mainfrom
chore/add-codespell-ignore-words
Aug 17, 2025
Merged

NiveditJain merged 4 commits into
mainfrom
chore/add-codespell-ignore-words

Conversation

@NiveditJain

Copy link
Copy Markdown
Member

No description provided.

@coderabbitai

coderabbitai Bot commented Aug 17, 2025 •

Copy link
Copy Markdown
Contributor

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated spell-check configuration to use an ignore list of common proper nouns and acronyms, reducing false-positive alerts in CI.
    • Simplified skip list formatting in the spell-check workflow for consistency.
    • No changes to application behavior, APIs, or documentation.

Walkthrough

Adds a codespell ignore file with 16 terms and updates the GitHub Actions spell-check workflow to pass that file to codespell via -I. No source code or public API changes.

Changes

Cohort / File(s) Change Summary
Spell-check config & workflow
.github/.codespellignorewords, .github/workflows/spell-check.yml
Added 16 ignore terms to .github/.codespellignorewords (file ends without a trailing newline); updated workflow step to run codespell with -I .github/.codespellignorewords in addition to the existing --skip list; minor formatting cleanup in the --skip list.

Sequence Diagram(s)

sequenceDiagram
  participant Dev as Developer
  participant GH as GitHub Actions
  participant Codespell as codespell
  participant Ignore as .github/.codespellignorewords

  Dev->>GH: Push/PR triggers spell-check workflow
  GH->>Codespell: Run codespell with --skip list and -I Ignore
  Codespell->>Ignore: Load ignore terms
  Codespell->>GH: Report findings excluding ignored terms
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my whiskers, CI aglow,
New names hop where linters go.
Exosphere, PagerDuty take flight,
I tuck them safe from spell-check sight.
Hooray — the checks stay calm tonight. 🥕✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between deec71b and 3805dd1.

📒 Files selected for processing (1)
  • .github/workflows/spell-check.yml (1 hunks)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/add-codespell-ignore-words

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Summary of Changes

Hello @NiveditJain, 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 introduces a new configuration file for codespell to ignore a predefined list of words. This change aims to reduce false positives during spelling checks by preventing codespell from flagging specific proper nouns, acronyms, and domain-specific terms as errors, thereby improving the accuracy of the spell-checking process.

Highlights

  • codespell configuration: A new file, .github/.codespellignorewords, has been added to the repository.
  • Ignored words: This file contains a list of words, including proper nouns, acronyms, and project-specific terms, that codespell should now ignore during its checks.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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. ↩

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

Copy link
Copy Markdown
Contributor

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 introduces a .codespellignorewords file to manage exceptions for the codespell linter. The added words are mostly project-specific terms and common acronyms. My review focuses on improving the maintainability of this new file by suggesting to sort the entries and to address a potential typo (expsphere) which might be better fixed in the source code.

Comment thread .github/.codespellignorewords Outdated
SDK
S3
Kusto
expsphere No newline at end of file

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

The word expsphere appears to be a typo of exosphere. It's recommended to fix typos in the codebase directly instead of adding them to an ignore list. This improves overall code quality and prevents confusion. Please consider removing expsphere from this list and correcting the typo in the source code where it occurs.

Comment thread .github/.codespellignorewords Outdated
@NiveditJain

Copy link
Copy Markdown
Member Author

@cursoragent remove expsphere from list of Ingored spellings

@cursor

cursor Bot commented Aug 17, 2025 •

Copy link
Copy Markdown

I updated the .github/.codespellignorewords file to refine the list of terms ignored by the codespell linter. This ensures that only necessary words are excluded from spell-checking, improving the accuracy of the linter.

  • I modified the .github/.codespellignorewords file.
  • I removed expsphere from the list of ignored words. This term is no longer required to be ignored by the codespell linter.
  • I also ensured the file now ends with a newline character, adhering to common file formatting best practices.

Open in Cursor Open in Web

Learn more about Cursor Agents

Co-authored-by: nivedit <nivedit@aikin.club>

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🔭 Outside diff range comments (1)
.github/workflows/spell-check.yml (1)

17-18: Pin codespell to a known-good version in CI

To avoid flaky builds when codespell’s dictionaries or behavior change, update .github/workflows/spell-check.yml:

  • File: .github/workflows/spell-check.yml, lines 17–18
          - name: Install codespell
  •   run: pip install codespell
    
  •   run: pip install codespell==2.4.1
    
  • If you’d like non-breaking bugfixes within the 2.4 series, use the compatible operator instead:
    run: pip install "codespell~=2.4.1"
  • Add a scheduled Dependabot/Renovate or GitHub Actions job to bump the exact version regularly (e.g. 2.4.1 → 2.4.2), run tests, and then update the pin once verified.

Latest stable release: 2.4.1 (Jan 28, 2025) [1][2]

Citations:

  1. https://pypi.org/project/codespell/
  2. https://github.com/codespell-project/codespell/releases
📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between fe7bae3 and 89a9572.

📒 Files selected for processing (2)
  • .github/.codespellignorewords (1 hunks)
  • .github/workflows/spell-check.yml (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-08-03T04:26:00.148Z
Learnt from: NiveditJain
PR: exospherehost/exospherehost#131
File: state-manager/app/models/executed_models.py:0-0
Timestamp: 2025-08-03T04:26:00.148Z
Learning: The exospherehost project is currently in beta phase, so breaking changes in APIs are acceptable and don't require versioning or migration strategies.

Applied to files:

  • .github/.codespellignorewords
🔇 Additional comments (2)
.github/.codespellignorewords (1)

1-17: Ignore list is case-sensitive; retain both lowercase and CamelCase entries

Codespell’s -I ignore file matches entries case-sensitively. A lowercase word will not suppress its capitalized form, so you do need to keep both variants (e.g. exosphere and Exosphere). No deduplication here—each casing you want to ignore must be listed explicitly.

References:

  • “words you put in ‑I must match the case you want ignored” (codespell README)
.github/workflows/spell-check.yml (1)

21-21: Good addition: using an ignore words file with codespell.

Adding “-I .github/.codespellignorewords” is the right move for maintainability.

Comment thread .github/.codespellignorewords Outdated
Comment thread .github/.codespellignorewords Outdated
Comment thread .github/workflows/spell-check.yml Outdated
Co-authored-by: nivedit <nivedit@aikin.club>
@NiveditJain
NiveditJain merged commit 1002eea into main Aug 17, 2025
@NiveditJain
NiveditJain deleted the chore/add-codespell-ignore-words branch August 21, 2025 08:24
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