shipper_adopt
shipper_adopt
Section titled “shipper_adopt”Adopt an existing GitHub issue or pull request into the shipper workflow. Pull requests are auto-detected and start at PR review; issues that already have a shipper label return a no-op success.
When to use
Section titled “When to use”Use this when an existing open GitHub issue should enter the shipper workflow at shipper:new, or when an existing PR should be adopted into Shipper at PR review without recreating the PR.
Behavior hints
Section titled “Behavior hints”- openWorldHint: true — The tool reaches GitHub or other external systems outside the MCP server.
Input schema
Section titled “Input schema”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| issue | integer | yes | - | GitHub issue or pull request number. |
Example call
Section titled “Example call”{ "issue": 99}Example result
Section titled “Example result”PR #99 adopted into shipper workflow for issue #42.Modified PR #99 by adding the shipper:pr-open label.Error modes
Section titled “Error modes”- Closed or merged PR: PR #
is closed or merged and cannot be adopted. - Draft PR: PR #
is a draft. Mark the PR ready for review before adopting it. - Fork PR: PR #
comes from a fork. Fork PRs are not supported for adoption in this release. - Already tracked: PR #
is already tracked by Shipper through issue # . No changes made. - Ambiguous closing references: PR #
references multiple open same-repository issues. Leave exactly one open closing reference before adopting. - Lookup, creation, or label mutation failure: Lookup/backing issue creation/label mutation failure: