shipper issue resolve-closure

shipper issue resolve-closure

Usage: shipper issue resolve-closure [options]

Resolve a GitHub closure hold

Arguments

Argument	Required	Description	Choices
	yes	Shipper issue ID, gh:, or GitHub URL	-

Flags

Long	Short	Value	Default	Description	Choices
—outcome	-		-	resolution outcome: not-planned, reopen, or complete	not-planned, reopen, complete
—reason	-		-	reason required when the outcome is not-planned	-
—confirmation-token	-		-	confirmation token returned by a completion preview	-
—json	-	-	false	output the result as JSON	-

Examples

Reopen the GitHub mirror and resume the saved workflow state.

shipper issue resolve-closure S#42 --outcome reopen

Preview the completion assertion and affected dependents.

shipper issue resolve-closure S#42 --outcome complete

Report dependent recovery impact, then resolve the hold as not planned.

shipper issue resolve-closure S#42 --outcome not-planned --reason "The request is no longer relevant"

Exit Codes

Code	When
0	The hold is resolved or a completion preview is returned.
1	The hold is absent, stale, locked, or remote restoration fails.

Constraints

• —outcome is required and has no default.
• --reason is required only for the not-planned outcome, is validated before repository lookup or mutation, and is stored verbatim as an ordinary attributed local note. Reopen and complete do not require it.
• The reason note and tombstone commit together, remain visible in closed issue detail, and use the ordinary note-retraction flow. Mirror-on projects the note as a GitHub comment; pending projection warns without undoing the local closure and is repaired with shipper issue reconcile --repair.
• Complete requires the current confirmation token returned by the preview; interactive use prompts after showing the assertion and dependents.
• Not planned previews and renders the same dependent recovery impact as direct close, then immediately applies its token without a confirmation prompt. A changed preview leaves the hold unresolved and requires retry.
• Not-planned returns preserve blocked state and blockers, move only Groomed through Planned to New, leave New, failed, and packaged dependents in place, and defer locked or closure-held dependents.
• Under --json, the not-planned human impact is written to stderr and stdout contains exactly one applied structured result.