Microsoft/vscode

Cloning in VSCode sets absolute worktree path. It breaks git on WSL. How to prevent VSCode from doing this unnecessary behavior?

Open

#275989 opened on Nov 7, 2025

View on GitHub
 (1 comment) (0 reactions) (1 assignee)TypeScript (74,848 stars) (10,221 forks)batch import
buggithelp wanted

Description

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.105.1 (user setup) Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084 Date: 2025-10-14T22:33:36.618Z Electron: 37.6.0 ElectronBuildId: 12502201 Chromium: 138.0.7204.251 Node.js: 22.19.0 V8: 13.8.258.32-electron.0 OS: Windows_NT x64 10.0.19044

Steps to Reproduce:

  1. Use "Clone Git Repository..."
  2. Run WSL on the repo's local directory
  3. Run git
  4. See git fail with "cannot chdir to .. no such file or directory"

Contributor guide

Tech stack
typescriptnodejs
Domain
developer experiencetooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScriptGit and WSL basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the VSCode Git extension source code in 'extensions/git' directory, particularly the clone command implementation that sets the worktree path. Look for any logic that converts paths to absolute Windows paths instead of using WSL compatible paths. Check if there are existing tests for cloning on WSL. The issue has one comment and an assignee; review that for any initial findings.