Repository navigation
Build first, then get a repo and hand over secrets to the platform team - #10
Merged
Merged
Conversation
Builders start in a folder on their computer, with no repo or org membership. When the app is ready, the platform team creates the repo in Virtual-Protocol, adds the builder, and adds the secrets the builder sends through a password manager share (only repo admins can set them). Then host, then deploy. The guide, README and the not-deployed-yet page now say so, and the guide tells Claude never to ask for a secret's value. 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.
Matches the bizops portal's new Build an app order (internal-bizops-tool#62): builders don't need GitHub org membership up front, and only repo admins can set Actions secrets.
The order now:
Changes
SKILL.md, version 1.1.0): new "How an app goes live" order. Claude starts new apps in a local folder (git init), runs them locally for the builder to try, and never asks for a secret's value. The hand-off now covers getting the repo, sending secrets to the platform team, hosting, then deploying.placeholder/server.mjs): "Add its secrets" becomes "Check its secrets are added". The page explains that the platform team adds them and asks for missing values by password manager share. The secrets-page buttons are marked "(admins)".Tested
claude plugin validate pluginpasses.🤖 Generated with Claude Code