chore: stop tracking .claude and ignore it - #136
Merged
Conversation
Local Claude Code configuration — slash commands and skills — is the operator's own tooling, not part of the provider client, and it was being published to a public repo with every clone. Nothing sensitive was exposed: the tracked files held public on-chain contract addresses and package paths, no keys or credentials. So this is untracked rather than purged from history, which would rewrite a public branch for no security benefit. They had also gone stale. All three describe the ZK-proof and UBI world removed in 677e37d — account creation with task-types 1,2,4, internal/contract smart contract bindings, Kubernetes — so anyone reading them was being told about a mode this client no longer has. The files stay on disk; only the tracking is removed.
flyworker
added a commit
that referenced
this pull request
Sep 6, 2026
#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. Co-authored-by: flyworker <ccao@swancloud.io>
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.
Local Claude Code configuration was tracked and shipping to a public repo with every clone:
git rm --cachedonly — the files stay on disk, so local tooling is unaffected.Nothing sensitive was exposed
I checked before deciding how to remove them. The only matches were public on-chain contract addresses and
internal/package paths — no keys, credentials, host paths, or links into the private tracker.So this is untracked, not purged from history. Rewriting a public branch would break every existing clone and fork for no security benefit, and the content is not a secret.
They were also stale
All three describe the ZK-proof and UBI mode removed in
677e37d— account creation withtask-types 1,2,4,internal/contract/smart contract bindings, Kubernetes. Anyone reading them was being told about a mode this client no longer has, which is the same class of problem #117 cleaned out ofdocs/..claude/added to.gitignore; verifiedgit check-ignorenow matches.