Default Workflows
Orbit ships a default workflow under orbit run. It wraps a seeded job pipeline under crates/orbit-core/assets/jobs/; the same pipeline is runnable directly via orbit run job <name>.
The workflow defaults --base to [workflow].base_branch from
config.toml, or main when it is unset. Pass --base <branch> to target a
different branch.
orbit run ship
Section titled “orbit run ship”Submit backlog tasks or one or more named tasks through the gated shipment pipeline. The default mode opens PRs; --mode local ships in-place. The command returns a run ID immediately, while dependency and lock waits happen inside the job.
orbit run shiporbit run ship "$TASK_ID"orbit run ship "$TASK_ID" "$SECOND_TASK_ID" --mode localorbit run ship "$TASK_ID" --base mainUnderlying job: task_auto_pipeline, which fans into task_gate_pipeline and then routes to task_pr_pipeline or task_local_pipeline from --mode.
Direct Job Execution
Section titled “Direct Job Execution”For schemaVersion 2 jobs without a workflow alias, invoke them directly:
orbit job listorbit run job task_auto_pipelineorbit run job task_auto_pipeline --input mode=localorbit run job task_auto_pipeline --waitA job run is submitted to a detached worker: the command prints the run ID and
returns as soon as the run is durable, without claiming its eventual outcome.
Pass --wait to block on the submitted run instead — it exits nonzero unless
the run succeeded.
Inspecting Runs
Section titled “Inspecting Runs”Every workflow run is durable. Inspect with:
orbit run history -j task_auto_pipelineorbit run show <RUN_ID>orbit run logs <RUN_ID>