shipper auth login
shipper auth login
Section titled “shipper auth login”Usage: shipper auth login
Sign in to Shipper
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| None | - | - | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| None | - | - | - | - | - |
Examples
Section titled “Examples”Start the interactive browser sign-in flow and save the returned license.
shipper auth loginRepeat sign-in to recover an expired or terms-outdated license.
shipper auth loginExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The core sign-in flow succeeds and returns the signed-in license decision. |
| 1 | The core sign-in flow fails; its failure message is surfaced unchanged. |
Constraints
Section titled “Constraints”- Every invocation starts the full interactive sign-in flow, even when a valid license is already present.
- A successful sign-in overwrites the existing machine-global credential record.
- Success output reads the user and grace-window end from the single decision returned by sign-in; unavailable optional facts are shown as
<unavailable>. - Core failures are not classified or rewritten by the command.
- The command works without Shipper settings, GitHub authentication, or a Git repository.
- The core sign-in flow still requires an interactive TTY.