You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
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:
The
.pixifolder 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
.pixifolder out of the projects root by usingdetached-environments = true?Beta Was this translation helpful? Give feedback.
All reactions