shipper issue close-not-planned
shipper issue close-not-planned
Section titled “shipper issue close-not-planned”Usage: shipper issue close-not-planned [options]
Close an issue as not planned
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| yes | Shipper issue ID, gh: | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —reason | - | - | reason the issue is being closed as not planned | - | |
| —json | - | - | false | output the result as JSON | - |
Examples
Section titled “Examples”Close a Shipper issue as not planned.
shipper issue close-not-planned S#42 --reason "Superseded by the new workflow"Exit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The issue is closed as not planned or was already not planned. |
| 1 | Resolution, locking, local-store, or GitHub cleanup fails. |
Constraints
Section titled “Constraints”--reasonis required, is validated before repository lookup or mutation, and preserves every non-blank character exactly as entered.- A successful closure commits the reason as an ordinary attributed local note headed
## Reason for Closing as Not Planned; it remains visible in the closed issue detail and can be retracted through the ordinary note-retraction flow. - The note and not-planned tombstone commit together in both mirror modes. Mirror-on projects the note as a GitHub comment and converges labels and closure afterward; projection debt is reported as a warning and can be repaired with
shipper issue reconcile --repair. - Retrying an already-not-planned issue still requires
--reason, but adds no second note or GitHub comment. - Before mutation, the command reports every dependent as returning to New, pending, unmoved, or already New; an empty structured
dependentsarray is rendered explicitly as no open dependents. - Groomed, Designed, and Planned dependents return to New. New dependents need no action; PR Open, Rework, Ready, and failed dependents remain unchanged. Legacy reviewed labels receive the same preservation as PR Open.
- Returned dependents remain blocked and keep every recorded blocker. Active-lock and closure-hold returns are durably deferred and applied automatically when movable.
- The report and closure are one command action with no confirmation prompt. Under
--json, the human pre-action report is written to stderr and stdout contains exactly one document with identity, outcome, and structured impact. - If the impact changes between preview and apply, the issue remains open and the command must be retried.