Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

15
  • Did you do an actual Git for Windows installation, or did you use Portable Git? Is git in your PATH? Commented Apr 30, 2015 at 16:05
  • 1
    @EdwardThomson I don't think I actually installed Git for Windows and that is exactly my problem. I didn't have git in PATH. I have various git's: GiHub client, SourceTree, Eclipse plugin, even cygwin. I added cygwin path to PATH just for the reason of curiosity and VS Code found it! Thanks for hint! Installing Git for Windows probably is still the right thing to do. (Now I need to figure out how to set the workspace properly so VS Code will not complain "This workspace isn't yet under git source control" but that will be a different question.) Commented Apr 30, 2015 at 16:49
  • Cool, I'll add this as an answer. Commented Apr 30, 2015 at 17:02
  • 6
    I have this problem, ONLY when running VS Code "as administrator", the git.path is not overridden in my normal user (non-admin) VS Code, but seems to find git just fine over there. Overriding git.path while in administrator mode (and then restarting VS Code) did not seem to help. My error: Git not found. Install it or configure it using the git.path setting. Commented Oct 5, 2018 at 14:35
  • 1
    UPDATE: I finally figured out that there's a system PATH variable, and then USER-specific PATH variables, and the Git was only in 1 of my user-specific PATHs Commented Oct 5, 2018 at 14:45