WSL2 repos should open in VSCode Remote

[pluma]

Describe the feature or problem you’d like to solve

When working with a repository from a WSL2 path (\\wsl$\<distro name>\<path>), launching VSCode will simply open the path as if it were a regular network path. As users using VSCode with WSL will most likely be using the Remote extension, this makes the "launch VSCode" button practically useless.

Proposed solution

GitHub Desktop should recognize that a repository path is a WSL2 path and offer to launch VSCode from within WSL rather than from Windows.

Additional context

This feature request was prompted by my question at Satellite 2020: https://github.com/githubevents/satellite2020/discussions/8#discussioncomment-10795

[outofambit]

Thanks for writing this up @pluma! Will be sure to take a look at this when we spend more time on WSL(2).

[just1a-person]

TL;DR

code.cmd gets run when you invoke code from cmd or powershell

code is a shell script that runs when you invoke code in WSL

[AlexStormwood]

This is the first Google search result when I search for "github desktop open vscode in wsl". It would be a hugely appreciated feature to simplify my dev workflow and surely the workflow for any other WSL-based developers.

[beingmerry]

Bumping this. GitHub desktop would be much more useful if I didn't have to do 2 clicks (1 to open, 1 to switch to WSL extension) when launching VS Code.

This should be a configuration change of changing the shell calling the commands. This looks possible and the intent under the Options > Integrations tab (see below) looks promising with drop-downs for External Editor and Shell, however; once changed to VS Code and WSL, VS Code still does not launch with WSL remoted in.

As an aside and to my surprise: searching WSL on GitHub docs returns nothing.

[beingmerry]

@outofambit hi! do you still work on the terminal team? Just wondering if this issue is on the radar. I think it would just involve piping the command through the Ubuntu terminal vs Cmd.exe