Worktrees

Use worktrees when one branch is reproducing an incident and another is active development.

Create an isolated environment

ldev worktree setup --name incident-123 --with-env
cd .worktrees/incident-123
ldev start

Why use it

• keep production-repro work separate from feature work
• compare fixes across branches
• avoid mixing runtime state between unrelated tasks

Runtime Note

Worktrees inherit the files that exist in the branch or commit used as their base.

If your project uses runtime storage overrides such as:

• docker-compose.postgres.volume.yml
• docker-compose.liferay.volume.yml
• docker-compose.elasticsearch.volume.yml

make sure those files already exist in the branch history before you create the worktree. A local copy in the main checkout is not enough if it has not been committed into the branch the worktree uses.

Clean up

ldev worktree clean incident-123 --force

Use this workflow only when isolation matters. Most day-to-day work does not need it.