Odoo + git worktree — develop hot, commit cold

The core tension: the dev instance mounts the main working tree (docker addons_path → the repo checkout), so you cannot switch branches without breaking the running registry — but the feature must stay off both production and the active dev branch (uat) until it is approved.

The pattern: the main tree stays on the dev branch and RUNS the code as uncommitted files; a git worktree holds a clean feature branch cut from production and RECEIVES the same changes as commits.

repo/                          ← main worktree, branch uat (env mounts this)
│   my_addon/        (untracked — live code the container executes)
│   other_addon/x.py (modified — your surgical fix)
└── .worktrees/feature-x/      ← second worktree, branch feature/x ← production
        my_addon/    (committed)