Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support WSL git #29812

jeasonstudio opened this issue Jun 29, 2017 · 7 comments

Support WSL git #29812

jeasonstudio opened this issue Jun 29, 2017 · 7 comments


Copy link

@jeasonstudio jeasonstudio commented Jun 29, 2017

I have installed git in wsl and how can I deploy it to my vscode

@vscodebot vscodebot bot added the git label Jun 29, 2017
@joaomoreno joaomoreno changed the title Using WSL for development and git does not work Support WSL git Jun 29, 2017
@joaomoreno joaomoreno removed their assignment Jun 29, 2017
@joaomoreno joaomoreno added this to the Backlog milestone Jun 29, 2017
Copy link

@ztolley ztolley commented Jun 30, 2017

To add to this. I'd like to be able to tell Visual Studio Code to not only allow you to tell the terminal to use WSL Bash but also configure it specify the path to the git client to use, or the shell, so that git commands issued use the WSL copy (so it picks up the ssh keys etc in that shell) and also run any git hooks in the bash shell too.

Copy link

@nguyenbathanh nguyenbathanh commented Aug 21, 2017

This should be great.

Copy link

@crewone crewone commented Aug 31, 2017

This would be great.

To illustrate the difference: git on windows does not properly handle symlinks (They seem to be invisible to NTFS in 'windows mode'), but WSL git properly handles these symlinks.

Copy link

@zmsy zmsy commented Sep 15, 2017

Very confusing for windows users to have two separate git client installs, two sets of ssh keys for the same service, etc depending on whether or not they're using wsl bash.

Would be excellent if setting the terminal as wsl bash automatically defaulted to using wsl git as well.

Copy link

@FistMeNaruto FistMeNaruto commented Sep 18, 2017

Facing the same issue

Copy link

@wasabigeek wasabigeek commented Oct 13, 2017

@zmsy I'm moving off topic, but shouldn't you be able to use a single set of SSH keys? When you do keygen, save them in /mnt/c/Users/USERNAME/.ssh - then you can add that same path when you use ssh-agent.

Correct me if wrong!

Copy link

@joaomoreno joaomoreno commented Nov 17, 2017

Duplicate of #9502

@joaomoreno joaomoreno marked this as a duplicate of #9502 Nov 17, 2017
@joaomoreno joaomoreno closed this Nov 17, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
9 participants