-
-
Notifications
You must be signed in to change notification settings - Fork 7
Could not find Git on the PATH - not recognized on windows #11
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
Comments
Thanks for logging, @fernfab! Please confirm, does the Git feature work out of the box in VS Code? |
I see a similar problem when git can only be found on the PATH, e.g. when extracting the portable distribution of git for Windows somewhere on disk and adding it to the PATH. In that case, the path returned from find-git-exec is just the string "git", rather than an absolute path as in all other cases. It stems from this line: https://github.com/TypeFox/find-git-exec/blob/master/src/find-git-exec.ts#L111. VS Code git integration works fine for me with this set up. You could use |
Thank you for help, @mcgordonite.
I am going to fix the issue and release a new version in the next days. Please bear with me. |
For the record; I am going to add a dependency to |
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. Closes #11. Signed-off-by: Akos Kitta <[email protected]>
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. Closes #11. Signed-off-by: Akos Kitta <[email protected]>
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. Closes #11. Signed-off-by: Akos Kitta <[email protected]>
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. Closes #11. Signed-off-by: Akos Kitta <[email protected]>
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. Closes #11. Signed-off-by: Akos Kitta <[email protected]>
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. Closes #11. Signed-off-by: Akos Kitta <[email protected]>
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. Closes #11. Signed-off-by: Akos Kitta <[email protected]>
@mcgordonite, can you please help to verify my changes? I have created a PR with the proposed fix: #12
Verifying it from a |
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. Closes #11. Signed-off-by: Akos Kitta <[email protected]>
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. - New version -> `0.0.2`. Closes #11. Signed-off-by: Akos Kitta <[email protected]>
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Use `execFile` instead of `spawn` to avoid broken pipes. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. - New version -> `0.0.2`. Closes #11. Co-authored-by: Alex Tugarev <[email protected]> Co-authored-by: Akos Kitta <[email protected]> Signed-off-by: Akos Kitta <[email protected]>
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Listen on the process' `close` instead of `exit`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. - New version -> `0.0.2`. Closes #11. Co-authored-by: Alex Tugarev <[email protected]> Co-authored-by: Akos Kitta <[email protected]> Signed-off-by: Akos Kitta <[email protected]>
- [win32]: Use `which` when cannot find Git on the `$PATH`. - Listen on the process' `close` instead of `exit`. - Moved the Windows build to Travis. - Pinned the versions with `yarn.lock`. - Bumped up the dependencies. - New version -> `0.0.2`. Closes #11. Co-authored-by: Alex Tugarev <[email protected]> Co-authored-by: Akos Kitta <[email protected]> Signed-off-by: Akos Kitta <[email protected]>
GH-11: Adjusted the lookup to the latest VS Code.
Message: "Could not find Git on the PATH"
OS - Windows 10 Pro
Git binaries on path:
C:\Users<user>\AppData\Local\Programs\Git\bin
Using git Bash:
which
/mingw64/bin/git
The text was updated successfully, but these errors were encountered: