heddle land

land is the managed-thread landing verb. It will refresh-then-merge for you when the replay is clean, and refuses rather than guessing when manual resolution is required — recover with heddle resolve, then heddle continue or heddle abort.

Landing squashes the thread by default. --no-squash preserves the per-state Git export instead. --threads a,b,c lands peer threads in order, each refreshed against the live target tip.

--dry-run previews the whole integration — thread to target, merge relation, conflicts, verify verdicts — with no mutation and no server round-trip. Note that a real heddle land does do network I/O, for the approval and branch-protection check.

There is no --push flag. Landing is local; publish afterwards with heddle push.

Flags

--thread <thread>

Thread to capture and integrate. default: current thread

--threads <a,b,c>

Peer threads to land in order. When --thread is also supplied, that thread is landed first. Each peer is refreshed and landed against the live target tip.

--message <message>, -m <message>

Intent/message to use if land needs to capture outstanding work first.

--no-squash

Preserve per-state Git export instead of squashing the landed thread.

--dry-run

Preview the integration without capturing work, syncing, or merging. No mutation occurs and no server round-trip is made.

Examples

Land one thread, then publish

bash$ heddle land --thread feature/auth$ heddle push

See also

• heddle ready
• heddle push
• heddle resolve