Skip to content

Add pattern to .geminiignore for Emacs versioned backups#1023

Open
mhucka wants to merge 1 commit intotensorflow:masterfrom
mhucka:add-to-geminiignore
Open

Add pattern to .geminiignore for Emacs versioned backups#1023
mhucka wants to merge 1 commit intotensorflow:masterfrom
mhucka:add-to-geminiignore

Conversation

@mhucka
Copy link
Copy Markdown
Member

@mhucka mhucka commented Mar 26, 2026

The addition of the pattern *.~*~ (for Emacs versioned backups) shouldn't be necessary because the file names should be covered by *~ in our .gitignore file, but Gemini CLI currently doesn't seem to interpret *~ that way. So, an addition to .geminiignore is needed to make Gemini CLI ignore Emacs versioned backups.

The addition of the pattern `*.~*~` (for Emacs versioned backups)
_shouldn't_ be necessary because the file names _should_ be covered by
`*~` in our `.gitignore` file, but Gemini CLI currently doesn't seem to
interpret `*~` that way. So, an addition to `.geminiignore` is needed to
make Gemini CLI ignore Emacs versioned backups.
Copy link
Copy Markdown

@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 .geminiignore file to explicitly ignore Emacs versioned backups, addressing a limitation in how the Gemini CLI interprets standard ignore patterns. Feedback was provided to refine the accompanying comment for better clarity and conciseness by removing conversational language and non-standard markdown emphasis.

@mhucka mhucka changed the title Add pattern for Emacs versioned backups Add pattern to .geminiignore for Emacs versioned backups Mar 26, 2026
@mhucka mhucka marked this pull request as ready for review March 26, 2026 22:36
@mhucka mhucka requested a review from MichaelBroughton March 26, 2026 22:48
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.

1 participant