chore: actually ignore .claude - #137
Merged
Merged
Conversation
#136 untracked the files but the .gitignore change never landed with them: the edit was unstaged when that commit was made, so only the deletions were recorded. Without this, recreating .claude puts it straight back under version control, which is the thing that was being fixed.
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.
Follow-up to #136, which was half-applied through my mistake.
That PR removed the three tracked files but the
.gitignorechange never landed with them — the edit was unstaged when the commit was made, so only the deletions were recorded:So
.claude/is untracked but not ignored: recreating it puts it straight back under version control, which is the thing #136 set out to prevent.This adds the rule on its own.