shipper unlock
shipper unlock
Section titled “shipper unlock”Usage: shipper unlock [options] [issue]
Release an issue lock or sweep stale locks
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| [issue] | no | Shipper issue ID, gh: | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —stale | - | - | - | release all stale locks | - |
| —force | - | - | - | force release a live run or operator pause after displaying its owner | - |
Examples
Section titled “Examples”Release the lock on S#42.
shipper unlock S#42Force unlock after inspecting the live holder.
shipper unlock S#42 --forceRelease all stale issue locks.
shipper unlock --staleExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The selected lock or stale locks are released. |
| 1 | Validation, issue lookup, or local lock cleanup fails. |
Constraints
Section titled “Constraints”- —stale cannot be used with an issue argument
- An issue argument is required unless —stale is used
- A live owner is never stale because of age. Targeted unlock first reports the issue, PID, and acquisition time; use —force only after reviewing those facts.
- Dead, corrupt, unreadable, or process-less records are reclaimable without —force. A forced retry removes only the exact lock token that was assessed.
- Troubleshooting: stale locks