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
Feature description
I would like to have the possibility to specify the relative folder location of the main worktree folder from the extension settings.
For example if I have a folder structure with 1 base directory that has 3 subdirectories like illustrated below and I open VSCode in the /base directory. I would like to be able to specify that the extension should use /base/subA for any actions connected to working with worktrees even though it is not the working dir in VSCode
/base
/base/subA
/base/subB
/base/subC
How would you use this feature?
I like having a repo structure as illustrated below but find the overhead of having each worktree in a separate VSCode window a bit annoying. Therefore having one vscode window in the parent dir of the separate worktrees makes switching topics easier but it is unfortunately not possible to manage worktrees from there
Example folder structure
/base (Not a git repo; vscode opened here)
/base/main/ (Git Repo; worktree main folder)
/base/featA/
/base/featB/
/base/bugfixA/
Having a setting like the following would help.
Default:
Worktree main folder location:
. /base
My setting:
Worktree main folder location:
./main /base/main
The text was updated successfully, but these errors were encountered:
@SkullYGD Hello, thank you for your feedback. However, I'm not quite sure I understand this approach.
On one hand, having too many files and worktrees in a VSCode workspace can be quite resource-intensive (due to file change listening and search queries being impacted). On the other hand, this plugin already provides the functionality to add directories to the workspace at any time, open a specific worktree's Git repository, and add a main directory to Git repository management. You can view any associated worktrees easily by either using the Quick Pick or opening the plugin's tree view.
Feature description
I would like to have the possibility to specify the relative folder location of the main worktree folder from the extension settings.
For example if I have a folder structure with 1 base directory that has 3 subdirectories like illustrated below and I open VSCode in the /base directory. I would like to be able to specify that the extension should use /base/subA for any actions connected to working with worktrees even though it is not the working dir in VSCode
How would you use this feature?
I like having a repo structure as illustrated below but find the overhead of having each worktree in a separate VSCode window a bit annoying. Therefore having one vscode window in the parent dir of the separate worktrees makes switching topics easier but it is unfortunately not possible to manage worktrees from there
Example folder structure
Having a setting like the following would help.
Default:
My setting:
The text was updated successfully, but these errors were encountered: