chore: untrack and ignore .claude/settings.local.json - #103
Merged
Conversation
Local editor settings were tracked in a public repository with no ignore rule. This is the same class of exposure found in Significant-Hobbies/live, where the equivalent file carried a live Turso credential. Starboard's copy contains no credential today — verified, only permission entries — so this is preventive rather than remedial. Untracks the file and adds the ignore rule that was missing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
What
Untracks
.claude/settings.local.jsonand adds the missing.gitignorerule.Why
This repo tracked a local editor settings file in public, with no ignore rule at all.
The same file in
Significant-Hobbies/livewas found to contain a live Turso auth token and database URL committed to a public repo. Starboard's copy contains no credential — I checked, it holds only Bash permission entries — so this change is preventive, not remedial.The failure mode is worth noting because
livehad the opposite problem: it did have the ignore rule, but the file was already tracked, and gitignore does not apply retroactively. Between the two repos that is both halves of the mistake.No code change, no behaviour change.
🤖 Generated with Claude Code