chore(claude): register the forest plugin marketplace - #367
Open
hercemer42 wants to merge 1 commit into
Open
Conversation
Installing the toolkit here meant adding the marketplace source by hand first. The committed entry makes `forest@forest` resolvable in this repo; it installs nothing on its own. `.claude/` was ignored wholesale, which excludes the directory itself, so a negation inside it never applies. Narrowing to `.claude/*` keeps every personal file ignored while letting the shared settings file be tracked. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Coverage Impact This PR will not change total coverage. 🚦 See full report on Qlty Cloud »🛟 Help
|
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.
Installing the Forest Claude Code toolkit in this repo currently takes two commands, the first of which nobody can guess:
This commits the marketplace source so only the second one is needed.
What the entry does, and does not do
.claude/settings.jsonregistersForestAdmin/claudineas a marketplace namedforestand marks theforestplugin enabled for this project. It installs nothing: a developer who has not run/plugin install forest@foresthas no plugin fetched, loaded or run for them — verified by putting an equivalent entry in a scratch repo for a plugin absent from this machine, opening a session there, and finding the plugin still absent from bothclaude plugin listand the install ledger.Access to the private
ForestAdmin/claudinecomes from the developer's own git credentials. There is no field for it here, and someone without access gets a resolution failure.Why
.gitignorechangesLine 23 was
.claude/, which excludes the directory itself — git never descends into it, so a!.claude/settings.jsonnegation would be dead text..claude/*excludes the entries instead, so the negation applies and only the shared settings file becomes trackable. Every personal file (settings.local.json, and every subdirectory) stays ignored.Refs: PRD-713
🤖 Generated with Claude Code
Note
Register
forestClaude plugin marketplace and track.claude/settings.jsonextraKnownMarketplacespointing toForestAdmin/claudineandforest@forestenabled inenabledPlugins.claude/*but negate.claude/settings.jsonso the config stays trackedMacroscope summarized 177bba2.