[Feature]: configurable worktree location

[danielo515]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

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

• I would be open to helping implement this.

[mhabegger]

This would be very helpful especially on Windows because of two reasons:

1. The dev drive usually runs ReFS and not NTFS, which is for small files. https://learn.microsoft.com/en-us/windows/dev-drive/
2. From company policy and attack surface reduction: the D-drive for depth is usually excluded from live scanning, https://learn.microsoft.com/en-us/defender-endpoint/microsoft-defender-endpoint-antivirus-performance-mode

[juliusmarminge]

#6975 proposes the same per-project worktree location with a literal path. It adds useful constraints: apply the setting server-side to desktop, mobile and PR-created threads, and allow the configured root in review/diff validation. Existing worktrees need not move.