Repository navigation
playbook 3.5.0
Units built in parallel
A work's plan now says which units can be built at the same time, and stage 6 builds them in parallel (work parallel-units, #42).
- Plan by batches. In stage 5 of
prepare-project, each unit names the units it waits for ("Waits for") and the paths it may change ("Changes"). The batches follow from that: batch 1 holds the units that wait for none, batch 2 those that wait only for batch 1, and so on. The plan also names the mostwriteagents at once and how a new worktree is prepared, such aspnpm installor copying.env. You accept all of it with the plan. - Parallel execution. In stage 6, each ready unit gets its own worktree from the work's branch, created with
git worktree add -b, and its ownwriteagent in the background. Each unit is reviewed from the main folder and merged with--no-ff. Then its worktree and branch are removed. A unit starts as soon as what it waits for is Done. - Shared worktree. When preparing a worktree is costly, a batch can share one worktree, with exclusive paths for each unit.
Nothing to migrate: the wiki format stays 5. A plan written before this version is built one unit at a time, as before. Units are also built one at a time without playbook-agents, and when the plan does not deliver through a work branch with local merges.