Skip to content

Comments

chore: gitignore claude settings#388

Merged
rootulp merged 1 commit intocelestiaorg:mainfrom
rootulp:rp/ignore-claude-local-settings
Feb 10, 2026
Merged

chore: gitignore claude settings#388
rootulp merged 1 commit intocelestiaorg:mainfrom
rootulp:rp/ignore-claude-local-settings

Conversation

@rootulp
Copy link
Collaborator

@rootulp rootulp commented Feb 10, 2026

Claude Code adds entries to a local file named .claude/settings.local.json and we don't want that file included in version control

@rootulp rootulp requested a review from jcstein February 10, 2026 14:58
@rootulp rootulp self-assigned this Feb 10, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @rootulp, 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 focuses on improving repository cleanliness and developer experience by ensuring that local configuration files for Claude Code are not tracked by Git. By ignoring these files, it prevents developer-specific settings from being committed, thus maintaining a cleaner repository and avoiding potential conflicts or accidental sharing of personal configurations.

Highlights

  • Gitignore Update: Added a new entry to the .gitignore file to exclude local Claude Code settings, specifically files matching .claude/*.local.json.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • .gitignore
    • Added .claude/*.local.json to ignore local Claude Code settings files.
Activity
  • No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.
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
Contributor

@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 updates the .gitignore file to exclude local settings for 'Claude Code'. I've suggested an improvement to ignore the entire .claude directory instead of a specific file pattern. This is a more robust approach that will prevent other local-only files from the tool from being accidentally committed in the future.

cips/wgs/**/*.html

# Claude Code local settings
.claude/*.local.json
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

To ensure all local settings and temporary files from 'Claude Code' are ignored, it's generally better to ignore the entire .claude directory rather than just specific files within it. This prevents other potentially local-only files created by the tool from being accidentally committed.

.claude/

Copy link
Member

Choose a reason for hiding this comment

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

agreed this is a good idea. wdyt @rootulp ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Gemini is wrong here. .claude/settings.json is actually intended to be included in version control and shared across teammates.

See https://code.claude.com/docs/en/settings#available-scopes

Screenshot 2026-02-10 at 10 52 25 AM

Copy link
Member

Choose a reason for hiding this comment

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

oops!

Copy link
Member

@jcstein jcstein left a comment

Choose a reason for hiding this comment

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

OK, but recommend gemini advice being implemented

@rootulp rootulp merged commit fb3b625 into celestiaorg:main Feb 10, 2026
4 of 5 checks passed
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