shipper priority

shipper priority

Usage: shipper priority

Set local priority on an issue and mirror priority labels

Arguments

Argument	Required	Description	Choices
	yes	Shipper issue ID, gh:, or GitHub URL	-
	yes	priority level	high, normal, low

Flags

Long	Short	Value	Default	Description	Choices
None	-	-	-	-	-

Examples

Mark S#42 as high priority.

shipper priority S#42 high

Clear explicit local priority.

shipper priority S#42 normal

Exit Codes

Code	When
0	Local priority is updated, possibly with GitHub synchronization pending, or already matches the requested priority.
1	Validation, issue eligibility lookup, or the local commit fails.

Constraints

• The local issue-state store is authoritative; GitHub priority labels are mirrors.
• Closed managed issues cannot be reprioritized in either mirror-on or store-only mode; the command exits with an error before writing priority.
• Priority changes and their mirror request commit atomically against fresh local state, preserving concurrent stage fields. Saved locally; GitHub delivery pending while a stage owns this issue. Delivery resumes at the next ordinary synchronization after the stage finishes. Lock release performs no GitHub work. Due work resumes at the next ordinary issue synchronization; an existing daemon or desktop runtime can deliver with Auto Ship disabled. CLI-only work remains saved after exit. Run shipper issue reconcile —repair to service delivery now; repair respects GitHub holds. Current store-only policy cancels requests.
• If label mirroring fails, run shipper issue reconcile --repair after resolving the GitHub problem.