Delivery
[Delivery](../glossary.md#delivery) is a local commit per repo and a `SUMMARY.md`; you merge and push.
Delivery is a local commit per repo and a SUMMARY.md; you merge and push.
What it is
Delivery is the local commit the run leaves you, plus SUMMARY.md. For each repository that passed, the factory writes one squashed commit on a shared branch. It does not merge that branch. It does not push. It does not open a pull request. Your merge, your push.
The commit is the change from the worktree, folded into one commit per repo so you can review it as a unit. Several repos on the same run share the branch name and a change-set id so you can see they belong together. SUMMARY.md is the one delivery note for that set.
If some repositories passed and some failed, the passed commits stay. The run ends as needs attention, partially delivered. You resume the failed repos on the same run, or you take the delivered commits and deal with the rest yourself. The factory will not push a half set for you.
What you see
After a successful deliver step you see a branch named for the task and run, one commit on each repo that passed, and SUMMARY.md in the evidence. The Dashboard calls a successful pipeline Delivered. Status in the CLI says the same in its own words.
SUMMARY.md names the task, the branch, how many repos were delivered, and the commits. Incomplete sets are marked as incomplete. That file is what you read before you merge, not a substitute for the diff.
Your checkout is still yours. The commit is on the factory's branch in each repo, made from the worktree. You check out that branch, or you merge it, when you choose. Until you do, main (or whatever base you configured) has not moved.
The factory never pushes. A green run on the Dashboard is not a green run on the remote. If you want a pull request, you open it.
What you decide
You decide whether to take the commit. Read the diff and SUMMARY.md. If you want it, merge and push with your usual git. If you do not, leave the branch, restart from the base, or ignore it.
You decide what to do with a partial delivery. Pushing only the repos that passed can strand the ones that failed. The summary warns you. Resume the failed repos when you want the same run to finish them; the delivered commits stay.
You decide where deliver sits in the pipeline. Last among the unattended steps is the usual place, after verify, maybe after a gate. Putting deliver earlier means a commit before the checks you still wanted.
You do not decide a remote, a pull-request template, or a merge queue. Those are yours, outside the factory.
Where to go next
Meet delivery as the deliver step, as the branch on each checkout, and as SUMMARY.md on the run.
- Evidence — the summary and the rest of the trail
- Run — when a run is delivered
- Multi-repo runs — one change-set, resume, restart
- Gates — looking before deliver
- Install — run the demo and inspect the branch it leaves