Before submitting
Area
apps/web
Problem or use case
Hello. I currently have some requirements on some of my projects that doesn't allow me to put them in arbitrary locations. For example, the current location of the worktrees. I want them to be children of the main project folder so I can take advantage of all my local tools configured for that particular folder.
Proposed solution
I want a setting that I can adjust per project to tell where to create the worktrees, either in a global place or as children of the current worktree.
Why this matters
As I said I use tools that are folder-dependent to handle my available dependencies, and they will not be available if you put the worktree in some random place.
Smallest useful scope
All the people using direnv and flakes on parent directories and similar stuff
Alternatives considered
NOt using worktrees
Risks or tradeoffs
This will be backwards compatible
Examples or references
No response
Contribution
Before submitting
Area
apps/web
Problem or use case
Hello. I currently have some requirements on some of my projects that doesn't allow me to put them in arbitrary locations. For example, the current location of the worktrees. I want them to be children of the main project folder so I can take advantage of all my local tools configured for that particular folder.
Proposed solution
I want a setting that I can adjust per project to tell where to create the worktrees, either in a global place or as children of the current worktree.
Why this matters
As I said I use tools that are folder-dependent to handle my available dependencies, and they will not be available if you put the worktree in some random place.
Smallest useful scope
All the people using direnv and flakes on parent directories and similar stuff
Alternatives considered
NOt using worktrees
Risks or tradeoffs
This will be backwards compatible
Examples or references
No response
Contribution