Pixi and Git Worktrees

[r-stiller]

What is the recommended workflow for Pixi environments when using Git worktrees?

I want to start using Git worktrees in my development workflow.
My typical project structure looks like this:

project-root/
.pixi/
.git/
pyproject.toml
src/
tests/

The .pixi folder is excluded from Git, but it can become very large (GBs).
When creating multiple worktrees of the same repo, each worktree ends up with its own environment, which increases disk usage and setup time.

Should I move the .pixi folder out of the projects root by using detached-environments = true?

[itcarroll]

I'm glad I'm not the first to consider this idea! I have a design question though. The package under src is typically installed in your environment in editable mode. If your worktree does not have its own environment, any changes under src won't affect the "installed" package. Is that okay for your workflow?