Repository navigation
Stop committing the shipmill plugin to .claude/settings.json - #112
Merged
Merged
Conversation
shipmill is each person's choice, not a requirement of the repo (shipmill/shipmill#702): install it at user scope instead. Co-Authored-By: Claude Opus 5.5 <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
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.
Deletes
.claude/settings.json, which only enabled the shipmill plugin and its marketplace for everyone who opens this repo.shipmill is each person's choice, not a requirement of the repo (shipmill/shipmill#702, building on spec 033 in shipmill/shipmill#707): a person who wants it installs it at user scope, and gate sessions load that install. A committed
enabledPluginsentry is the likely trigger for the project-scope installs that come back on the host and lag behind releases.🤖 Generated with Claude Code