Git Worktree Support

[jonny-harte]

The Salesforce VSCode extension does not currently work correctly when using Git worktrees, making it difficult to adopt modern Git workflows that are increasingly common in enterprise development.

Current Behaviour

When using Git worktrees, the SF extension fails to resolve the correct project root, resulting in the following error when attempting to deploy or retrieve metadata:

Error deploying or retrieving source: The file or directory that you tried to deploy or retrieve isn't in a package directory that's specified in your sfdx-project.json file.

Additionally, org configuration (.sf/config.json) is not inherited by worktrees, requiring each worktree to be manually configured with a target org — or falling back to a global default which conflicts with multi-project setups.

Expected Behaviour

• The extension should correctly resolve sfdx-project.json from within a worktree
• Org configuration should be discoverable from a parent directory, consistent with how the SF CLI resolves config in other contexts
• Worktrees should be treated as first-class project roots by the extension

Use Case

Git worktrees are particularly valuable for Salesforce consultants and developers who need to:

• Run AI coding agents (e.g. Claude Code, GitHub Copilot) in isolated worktrees while continuing work in the main repo
• Switch context between branches (e.g. feature work, UAT, hotfix review) without stashing or committing
• Maintain permanent worktrees for long-lived branches (main, UAT, staging) alongside active development branches

Without worktree support, developers are forced to maintain separate clones of the same repository, which is exactly the problem worktrees are designed to solve.

Environment

• Salesforce Extension Pack (latest)
• VS Code
• SF CLI 2.123.1
• macOS

Suggested Solution

1. Walk up the directory tree from the active file to find sfdx-project.json, respecting worktree boundaries
2. Allow .sf/config.json to be resolved from a common parent directory shared by all worktrees
3. Add a dedicated Worktrees view or first-class worktree awareness similar to GitLens Pro