Vscode compare folders and files code#

Dependency on the VS Code Git extension means that if there is a bug or a missing feature, we are not fully in control, and we can only contribute the fix upstream and wait for a release.However, there is a drawback of using the VS Code Git extension: There is no drawback (that I can think of) of changing the abstraction. Running the git commands ourselves is tricky from a security perspective (e.g. Less dependency on execa module to run our custom git commands and parse them.Single source of truth for the git information, if user sees 4 repostiories in the SCM tree view, they'll see up to 4 in the GitLab Workflow TreeView.Benefits of switching to the VS Code git extension.Easy to understand for new and existing contributors. Folder that contains multiple repositories explorer We've recently introduced the VS Code Git extension to our codebase ( Support VSCode 'git clone' command) and now we can use the way VS Code recognizes repositories. The key insight is that the workspaceFolder git repository 1:n relationship makes it very hard to keep the extension git information in sync with VS Code.

🐞 Does not support workspace folders containing multiple repositories.workspace folder contains two repositories. ) - ❌ The extension will run git command in the folder called worskpace and think that there are no repositories. 🐞 Open active file on GitLab does not resolve from git repository root.) - ⚠️This now works, because there is still only one repository for the workspaceFolder. Open frontend ( cd workspace/projectA/frontend & code.) - ✅ This will work fine because the workspaceFolder is a git repository at the same time Open projectB ( cd workspace/projectB & code.This structure allows for the following three scenarios:

Vscode compare folders and files