shipper repo delete
shipper repo delete
Section titled “shipper repo delete”Usage: shipper repo delete [options]
Confirm removal of every registration after existing work drains
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| yes | - | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —yes | - | - | - | Confirm deletion without prompting | - |
| —dry-run | - | - | - | Preview deletion effects without changing state or starting a host | - |
| —json | - | - | - | Return one JSON result; prompts go to stderr | - |
Examples
Section titled “Examples”Preview all effects without starting deletion.
shipper repo delete owner/name --dry-run --jsonConfirm identity-wide deletion directly.
shipper repo delete owner/name --yesExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | Preview, cancellation, or accepted deleting/deleted/unchanged result. |
| 1 | Invalid target, missing non-interactive confirmation, unavailable host, refusal or uncertain acknowledgement. |
Constraints
Section titled “Constraints”- Default No. Dry-run takes precedence over —yes. Deletion turns Auto-ship off, stops automatic work at safe checkpoints and lets admitted manual work and live questions finish. New work, add and enable refuse while pending. All registrations are removed atomically after drain; issue content/history, settings and checkouts remain. JSON writes one result to stdout and prompts on stderr. Inspect progress with repo list or status; retry the same identity after uncertainty. Current Shipper builds durably admit repository work before effects: pending deletion drains admitted manual queues and live questions, while automatic work stops at existing safe checkpoints. Normal Desktop Quit may close the UI while its main process or a capable daemon keeps deletion and protected sessions alive; reopening reattaches those sessions. Older unadmitted builds are outside this execution guarantee. Builds containing df2234313 refuse incompatible saved records before access or repair; this does not promise uninterrupted legacy execution. An unregistered identity returns unchanged without starting a host. After completion, register an alias again to use retained content/history with Auto-ship off.