Account
Your Patchwing account covers sign-in, organization collaboration, and CI authentication. The console and the CLI share the same apps and organizations, with independent sessions.
Account and sign-in
Section titled “Account and sign-in”- Registration verifies your email and sets a password without a separate name step. Subsequent console sign-ins use email and password.
- Reset a forgotten password using email verification; a successful reset revokes all existing sessions.
- The CLI signs in with
pw login: it opens a dedicated email-code authorization page and returns to a local callback. This is separate from console password sign-in. - Signing out only revokes the current session; CLI and console sessions on other machines are unaffected.
Organizations and permissions
Section titled “Organizations and permissions”- Apps belong to organizations; a personal organization is created automatically when you register.
- Access within an organization is granted by role:
owner,admin, andappManager. - Use the console to create apps and inspect releases, patch artifacts, and rollback status.
CI authentication (API keys)
Section titled “CI authentication (API keys)”Non-interactive environments such as CI runners authenticate the CLI with an account-level API key via the PATCHWING_TOKEN environment variable:
- Store credentials in the runner's secret store — never in workflow files, source, or logs.
pw login:cihas been removed; use API keys instead.- Validate credential provisioning together with runner signing and tooling; if a credential leaks, reset the password and revoke sessions immediately.
Security tips
Section titled “Security tips”- Don't commit login credentials or API keys to source control.
- Inject credentials in CI through environment variables or a secret management service.
- Sign out after using shared machines to avoid shared sessions.