Repository navigation
chore: stop turning on internal Claude plugins - #38
Conversation
|
Warning Polylane could not verify the production impact of this pull request. The only change is the deletion of Also considered · 1 refuted
Analysed against 2 cloud accounts and 1 repository
Polylane could not find the cloud resources this repository manages, so this review looked at the entire cloud account. Connect this repository to its resources and the next review will focus on exactly what this code deploys to. Polylane analysed Rate this review: 👍 helpful · 👎 not helpful · 😕 confusing |
bf0743e to
3854a8d
Compare
The internal datum-platform and datum-gtm plugins are moving to a private marketplace in datum-cloud/infra, which employees set up once on their own machine. Committed settings no longer register the old marketplace or enable those plugins, so Claude Code won't rewrite this file once they are removed from the public catalog.
3854a8d to
ad38ff0
Compare
ecv
left a comment
There was a problem hiding this comment.
Approve.
The change removes only the marketplace entry and the two plugin enables from .claude/settings.json. Every other setting in the file stays as it was, and the file still parses as JSON.
Follow-ups:
- The platform and go-to-market plugins move to the private marketplace in datum-cloud/infra#7587, which is still open. If this merges first, sessions in this repo lose those plugins until people add that marketplace themselves.
Requested by Scot Schuchert-Wells · project thread
This repo's committed Claude Code settings turn on the internal datum-platform and datum-gtm plugins for everyone who opens it. Those plugins are moving to a private marketplace in the infra repo, which employees set up once on their own machine. This change removes the old marketplace and plugin settings so the public catalog can drop them without leaving a dirty settings file behind. Nothing else in the repo changes.
Test plan
Generated by Claude Code