chore: ignore the per-machine Claude Code state, not the reviewable half - #21
Merged
Merged
Conversation
These paths are per-machine: a session handoff, one machine's permission grant, and where present the throwaway checkouts a subagent runs in. Untracked and unignored, the first permission grant on any other checkout makes `git status` report a change that is not one — a standing false finding in an instrument whose whole value is that a finding means something. Scoped rather than blanket: `.claude/settings.json` is reviewable configuration and stays trackable if this repository ever adds one.
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
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.
What
Ignore
.claude/sessions/,.claude/settings.local.jsonand.claude/worktrees/.Why
These are per-machine: a session handoff, one machine's permission grant, and — where present —
throwaway checkouts of this repository that a subagent runs in.
Left untracked and unignored, the first permission grant on any other checkout makes
git statusreport a change that is not one. That is a standing false finding in aninstrument whose whole value is that a finding means something, and it is currently
reproducing: this repository reads dirty to
git statuswhile its working tree is in factclean.
Why not
.claude/wholesale.claude/settings.jsonis reviewable configuration — a hook nobody can read is a hook nobodycan correct — so it stays trackable if this repository ever adds one. Only the paths that can
never be reviewed are ignored.