shipper block
shipper block
Section titled “shipper block”Usage: shipper block [options]
Record that an issue is blocked by other issues/PRs
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| yes | target issue number | - | |
| <blockers…> | yes | one or more blocker issue/PR numbers | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —reason | - | - | optional free-text reason | - |
Examples
Section titled “Examples”Record that issue 42 is blocked by #17.
shipper block 42 17Record multiple blockers with an explanatory reason.
shipper block 42 "#17" "#29" --reason "Waiting for both dependencies."Exit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The blocked label and additive blocked comment are recorded. |
| 1 | Validation, issue lookup, blocker lookup, label mutation, or comment creation fails. |
Constraints
Section titled “Constraints”- At least one blocker issue or pull request number is required.
- Blocker references must be same-repository issue or pull request numbers.
- The target cannot block itself, and each blocker must exist and still be open.