Skip to content

Untrack the local Claude permissions file - #31

Merged
panyam merged 1 commit into
masterfrom
chore/untrack-claude-settings
Sep 21, 2026
Merged

panyam merged 1 commit into
masterfrom
chore/untrack-claude-settings

Conversation

@panyam

@panyam panyam commented Sep 21, 2026

Copy link
Copy Markdown
Owner

What changes

Removes docs/.claude/settings.local.json from the repo and adds **/.claude/settings.local.json to .gitignore. The file stays on disk, it just stops being tracked.

It went in with #29 by accident. That PR did git add docs and swept up an untracked directory alongside the content changes. The file records one machine's tool permissions, so it should never have been committed.

No source, docs content or build behaviour changes.

Reviewer's guide

Two files, both one line of intent. .gitignore gets the pattern at any depth rather than anchored at the root, since the stray copy was under docs/ and a root-anchored pattern would not have caught it.

  1. .gitignore
  2. docs/.claude/settings.local.json, deleted from the index

Risk / blast radius

  • Anyone with the file already checked out keeps their local copy untouched, since this only removes it from the index.
  • Nothing reads the file except Claude Code on the machine that wrote it.

docs/.claude/settings.local.json went in with PR 29 by accident, picked up
by a git add of the docs directory. It records one machine's tool
permissions and has no business in the repo.
@panyam
panyam merged commit aac1520 into master Sep 21, 2026
6 checks passed
@panyam
panyam deleted the chore/untrack-claude-settings branch September 21, 2026 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant