Update .gitignore file and add a .geminiignore file
#923
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds some more patterns to
.gitignorefor some of the tools known to be used by the TFQ developers. Although these sorts of common ignore patterns are better put in an individual user's global gitignore file (something that can be configured in git), it turns out that Gemini CLI also reads the.gitignoreto determine what files to ignore in a project. Making the project.gitignorefile more comprehensive thus helps us use AI code assistants more effectively.This commit also adds an initial
.geminiignorefile for Gemini CLI. Gemini CLI reads.gitignoretoo, but.geminiignoretakes precedence; this is essential for un-ignoring files that shouldn't be committed to git yet should be visible to Gemini CLI.