shipper adopt
shipper adopt
Section titled “shipper adopt”Usage: shipper adopt [options] [ref]
Adopt an existing issue or pull request into the shipper workflow
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| [ref] | no | issue or pull request number | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —all | - | - | false | adopt all open issues without shipper labels | - |
Examples
Section titled “Examples”Adopt one existing issue into the workflow.
shipper adopt 42Adopt an existing PR and start its backing work item at PR review.
shipper adopt 17Adopt every open issue that does not already have a Shipper workflow label.
shipper adopt --allExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The selected issue or PR is adopted, or the selected issues are labeled successfully. |
| 1 | Validation, lookup, PR eligibility, backing issue creation, or label mutation fails. |
Constraints
Section titled “Constraints”- —all and an explicit issue or pull request argument are mutually exclusive
- An issue or pull request argument is required unless —all is used
--allremains issue-only; there is no bulk PR adoption mode.- Adoptable PRs must be open, non-draft, and use a same-repository branch.
- A PR with one open same-repository closing reference uses that issue as its work item; a PR with none creates a tracking issue; a PR with multiple is rejected as ambiguous.
- A PR whose backing issue already has a
shipper:*label is rejected as already tracked.