gitignore: Ignore entire .claude/ directory#50
Open
kidskoding wants to merge 1 commit into
Open
Conversation
Author
|
@peter-lockhart-pub please review as soon as possible, follow up as additional PR based off #44. thanks! |
Local Claude Code skills and settings live under .claude/ and shouldn't be tracked. The prior rule only covered one skill subdirectory; broaden it to the whole directory. Signed-off-by: Anirudh Konidala <kidskodingclub@gmail.com>
kidskoding
force-pushed
the
gitignore-claude-dir
branch
from
1a18736 to
46da301
Compare
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.
Upon request in #44 thread by @peter-lockhart-pub
Local Claude Code skills and settings live under .claude/ and shouldn't be tracked. The prior rule only covered one skill subdirectory; broaden it to the whole directory
Just an fyi, these skills that were gitignored are used to help assist in the codebase, such as finding good issues to tackle and understanding what the codebase does from a technical standpoint. Some do assist in code, where disclaimers will be written when done so, but code will still carefully be checked, reviewed, and tested via a human before sending in a PR