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 current workflow when opening a worktree (inside of the existing window and in a new window) is to use the openFolder way with the worktrees root folder.
If i have a .code-workspace file (see multiroot-workspaces), that was used to open my current window, the new window is still only opened from the folder without using the workspace file. vscode then shows me a hint that it found a workspace file and if i want to open it. But this reloads the window what requires unnecessary time, especially in devcontainer setups.
Expected Behavior
I expect gitlens to use the "open workspace from file" way from vscode if a .code-workspace file was used to open the current window. This saves time and improves the user experience.
The vscode api does provide the information if and which workspace file is currently opened. See workspace.workspaceFile. This way it is easy to find out if the current window is opened from a workspace file and to get the Uri of that file. If the same file exists in the worktree that is to be opened it can be opened with the vscode.openFolder command and the workspace file's Uri.
The text was updated successfully, but these errors were encountered:
Looks like worktree.ts:1091 is the place where the check of the vscodes api workspace.workspaceFile and then usage of the worktree file's uri would be necessary.
Current Behavior
The current workflow when opening a worktree (inside of the existing window and in a new window) is to use the
openFolder
way with the worktrees root folder.If i have a
.code-workspace
file (see multiroot-workspaces), that was used to open my current window, the new window is still only opened from the folder without using the workspace file. vscode then shows me a hint that it found a workspace file and if i want to open it. But this reloads the window what requires unnecessary time, especially in devcontainer setups.Expected Behavior
I expect gitlens to use the "open workspace from file" way from vscode if a
.code-workspace
file was used to open the current window. This saves time and improves the user experience.The vscode api does provide the information if and which workspace file is currently opened. See workspace.workspaceFile. This way it is easy to find out if the current window is opened from a workspace file and to get the Uri of that file. If the same file exists in the worktree that is to be opened it can be opened with the
vscode.openFolder
command and the workspace file's Uri.The text was updated successfully, but these errors were encountered: