chore: ignore .claude/, Claude Code's local state - #62
Merged
Conversation
Claude Code writes per-session settings and scratch worktrees under .claude/. It is local tooling state, not repo configuration -- nothing in it changes how the optimizer builds, tests or serves -- so it should not arrive in a diff.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds
.claude/to.gitignore.Claude Code writes two things there: per-session
settings.json, and scratch git worktrees under.claude/worktrees/. Both are local tooling state rather than repo configuration — nothing in the directory changes how the optimizer builds, tests or serves — so it should not show up as untracked noise ingit statusor arrive in anyone's diff.Ignoring the directory wholesale is the simple call. The alternative is to track
.claude/settings.jsonas shared team config and ignore only.claude/worktrees/andsettings.local.json. That is worth doing if you ever want hooks or permissions committed for whoever picks the repo up, but there is nothing in the current settings file worth sharing — it holds a single local worktree-isolation flag.Test plan
git check-ignore -v .claude/settings.jsonresolves to this rulegit statusis clean on a fresh checkout.claude/was ever committed, so this changes no history