Repository navigation
playbook 2.6.0
prepare-project now asks how a work is delivered, before any code.
- At stage 5 (Plan), it asks where the work is tested: on its own branch, deployed for instance from a worktree; on a shared test branch; or nowhere apart. It assumes no branch name such as
stagingormain. - It reads the project's own delivery skill and the git history first, as sources, and offers three ways to integrate the units, each with its cost: one pull request for the whole work; a work branch with a draft tracker pull request, reaching the test branch by one merge; or each unit straight to the test branch.
- It recommends branch names such as
feat/user-loginandfeat/user-login-01-core, unless the project has its own convention. - When a choice would leave an unfinished work where people test, it names the risk and recommends a way that keeps that branch whole. You decide.
- At stage 6 (Execution), the work closes only after you check it where it is tested; fixes from that check are units of the same work.