docs: public install in README; internal package + split in CONTRIBUTING - #12
Merged
Conversation
…kage split to CONTRIBUTING README now installs the public reply-cli from npm. The GitHub Packages instructions and the public/internal split move to CONTRIBUTING. Co-Authored-By: Claude Opus 4.8 (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.
Public readers were getting the internal GitHub Packages install instructions. Fixed:
npm install -g reply-cli. No scope/registry/auth config; that's all gone from the public-facing docs.reply-clipublic vs@reply-team/reply-clion GitHub Packages, same source/bin, public = promoted internal tag) and the internal-build install steps (scope + read:packages token) moved here.Ref: REPLY-51236