shift-cli stage

Stage manages sandbox sessions, published Stage apps, Google scope declarations, and optional GitHub repository links.

Usage

shift-cli stage <subcommand> [arguments] [flags]

Core Commands

shift-cli stage new --json
shift-cli stage push ./my-app -s <session-id> --json
shift-cli stage status -s <session-id> --json
shift-cli stage apps --json
shift-cli stage scopes:set -s <session-id> --scope https://www.googleapis.com/auth/drive.readonly --json
shift-cli stage repo status --json
shift-cli stage repo connect --json

Repository Commands

Command	Description
stage repo status [app-id]	Show the repo linked to a Stage app
stage repo connect [app-id]	Link local git or manual GitHub metadata
stage repo disconnect [app-id]	Remove the linked repo
stage repo local	Inspect local .shift/stage-app.config.json
stage scopes:set -s <session-id> --scope <scope>	Store Google OAuth scopes for a Stage session

Related Testing Commands

Stage app testing uses top-level platform commands:

Command	Description
shift-cli token create	Mint a delegated local test grant
shift-cli token list	List active delegated grants
shift-cli test bootstrap	Create a one-time browser bootstrap artifact

Notes

• shift-cli create-app writes .shift/stage-app.config.json and usually creates the Stage app up front.
• If the Stage app has a linked GitHub repository and local git is available, stage push will commit and push local changes before the Stage upload.
• Git sync failures are warnings; they should not block the Stage deploy.