Visual Studio Code cannot detect installed Git

Question

Visual Studio Code reports "It look like git is not installed on your system." when I try to switch to the git view. I know I have git installed and used by other Git clients. I guess if I reinstall Git following Visual Studio Code's instruction ("install it with Chocolatey or download it from git-scm.com"), it probably can fix the problem, but I don't want to mess up the existing Git clients on my system. Is there a reliable way to configure Visual Studio Code so it can find existing git installation?

Answer 1

For macOS users, my issue was that the macOS Privacy settings had Cursor/Code turned off for access to Files and Folders in Settings > Privacy. Once I enabled it (gave Cursor access to it), the "git missing" problem was resolved.

Answer 2

Update 2020 (Mac)

I went through this $h!† again after updating to macOS v10.15 (Catalina), which requires an Xcode update.

And to clarify, while this post is about Visual Studio Code, this issue, is system wide. Your Git install is affected/hosed. You can try to run git in your terminal, Bash, Z shell (zsh), or whatever. It is now and it just won't.

There are two possible fixes:

• Just update Xcode. Start it up and agree to the license. That's it.
• Or run sudo xcodebuild -license in a Terminal

---

I hit this on Mac/OS X.

Symptoms:

• You've been using Visual Studio Code for some time and have don’t have any issues with Git
• You install Xcode (for whatever reason - OS update, etc.)
• After installing Xcode, Visual Studio Code suddenly "can't find Git and asks you to either install or set the Path in settings"

Quick fix:

Run Xcode (for the first time, after installing) and agree to license. That's it.

How I stumbled upon this "fix":

After going through numerous tips about checking git, e.g., which git and git --version, the latter actually offered clues with this Terminal message:

Agreeing to the Xcode/iOS license requires admin privileges, please run “sudo xcodebuild -license” and then retry this command.

As to why Xcode would even wrap it's hands on git, WAT.

Answer 3

Now you can configure Visual Studio Code (version 0.10.2, check for older versions) to use an existing Git installation.

Just add the path to the Git executable in your Visual Studio Code settings (menu File → Preferences → Settings) like this:

{
    // Is Git enabled
    "git.enabled": true,

    // Path to the Git executable
    "git.path": "C:\\path\\to\\git.exe"

    // Other settings
}

Answer 4

Although many people answered already, but for me it the installation method or path setting wasn't the cause of problem. Maybe future version of VSCode might show the proper error message, but it was the bad .gitconfig configuration causing VSCode to undetect git. So, as someone might answered, if path setting doesn't work for you, might check git status first would be good.

Answer 5

macOS - Visual Studio Code.

Step 1: Go to Visual Studio Code, menu File → Preferences → Settings (or Ctrl + ,).

Step 2: Type 'Path' in the search bar. You will get a result list that contains Git.

Step 3: Click on Git. After that, click on Edit in settings JSON file.

Step 4: In your Mac Terminal, type which git. You will get the Git path

Step 5: Just copy that path and add again the path key in the JSON file.

Answer 6

For Mac

First, type

git

in the terminal and see what error you are getting.

Then:

If the error is related to a command line tool!

Run:

xcode-select --install

And

Just go ahead and go through this answer. For Mac especially. It worked very easily for me:

Why am I getting an “invalid active developer path” when attempting to use Git after upgrading to macOS Ventura?

Answer 7

Upgrade to macOS v13 (Ventura) < 13.0

As of November 2022

Upgrading to macOS v13 (Ventura) does not seem to affect your coding environments too much.

After upgrading to macOS v13, your Terminal and Visual Studio Code will give off a few errors. Such as:

It looks like Git is not installed on your system ..

or

can't find Git and asks you to either install or set the Path in settings

Some errors depend on your Z shell (zsh) setup or other customizations.

These common problems can be resolved by simply by reinstalling the Xcode command-line tools and updating Homebrew - since your terminal might be affected, reinstall from Apple's executable https://developer.apple.com/download/all/ developer.apple.com. You will need to log in with your Apple ID.

Once installed, update Homebrew:

brew upgrade

Mac M1 - M2 machines likely have some native and ARM applications, so run:

arch -arm64 brew upgrade

Close all terminals and Visual Studio Code to restart!

Reopen Visual Studio Code, and the errors should be gone.

If Visual Studio Code is still looking for the Git path, you will need to add it manually.

Find the Git location and copy from the terminal:

which git

And add the path to the Git executable in your Visual Studio Code JSON settings file (menu File → Preferences → Settings) find and update the line. It should look similar to:

"git.path": "/usr/local/bin/git",

Answer 8

I had the same issue after updating my macOS to macOS v13 (Ventura)!

I used the following command and it worked for me!

git --version

To confirm if you have Git installed already and if not run

brew install git

to install the latest version.

After a successful installation, run

brew link git

to link the path and if it says Could not symlink because target already exist*, you can run

brew link --overwrite git

to overwrite it.

Answer 9

On Windows 10:

My problem was that I cloned the repository with PowerShell started in Administrator mode. When I don't start PowerShell in system Administrator mode, Visual Studio Code can detect the Git repository.

Answer 10

I faced this issue after updating macOS!

I installed Git again using Homebrew, and it worked!

brew install git

Answer 11

Windows 10

Nothing helped me from the answers. The problem appeared in IntelliJ IDEA and Visual Studio Code.

The Git tab in Visual Studio Code offered me to Init the Repository. It didn't detect that there was a .git folder in the workspace.

When I performed a git pull from a console in Visual Studio Code, it asked me to add credentials by the web browser. After I was logged in, the Git problem was fixed and all plugins started working. I needed to do that for each cloned repository even if I used proper credentials during a git clone ... command.

PS. I cloned the repository from GitLab by HTTPS on Windows using CMD. Visual Studio Code uses PowerShell, and that might be the reason.

Answer 12

It worked for me just by installing Git for Windows from Download for Windows.

There wasn't any need to set environment variables or path.

Context: I had installed Visual Studio Code, and GitHub Desktop. I cloned the repository using GitHub Desktop.

When I opened the repository, using Visual Studio Code, I saw this error.

I resolved it by installing Git for Windows.

Answer 13

The only way I could get to work in my Windows 8.1 is the following:

Add to system environment variables (not user variables):

C:\Users\USERNAME\AppData\Local\GitHub\PortableGit_YOURVERSION\bin;C:\Users\USERNAME\AppData\Local\GitHub\PortableGit_YOURVERSION\libexec\git-core;C:\Users\USERNAME\AppData\Local\GitHub\PortableGit_YOURVERSION\cmd\

This fixed the "it looks like Git is not installed on your system" error on my Visual Studio Code.

Answer 14

I solved the same problem on macOS with an M1 Pro processor by installing the GitLens Visual Code extension. The changed files were displayed after enabling the extension. Then I turned to reloading Visual Studio Code and there were no changes, but once I ran

git status

in the terminal, it showed all the files, and all changes were tracked.

Answer 15

Run xcode-select --install. It'll prompt you to install command line developer tools. Install the tools and restart your Visual Studio Code.

You'll see Git working once again in Visual Studio Code.

Answer 16

I ran into this problem after upgrading my macOS to macOS v12 (Monterey).

It turned out that Xcode has been removed in the new update from my mac. I Just tried the following suggested solution:

Git is not working after macOS update ("xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools")

Answer 17

If Git is missing after the OS update, in my case macOS v11 (Big Sur), just literally:

brew install git

Answer 18

Follow this:

1. Menu File → Preferences → Settings
2. In search, type &rarr the path to the Git executable
3. Now scroll down a little. You will see the "Git:path" section.
4. Click "Edit in settings.json".
5. Now just paste this path there: "C:\Program Files\Git\mingw64\libexec\git-core\git.exe"

---

Restart Visual Studio Code. Open a new terminal in Visual Studio Code and try "git version".

---

In case the problem still exists:

1. Inside the terminal, click on the terminal options (1:PowerShell)
2. Select Default shell
3. Select Bash

Open a new terminal and change the terminal option to 2:Bash. Again, try "git version". This should work :)

Answer 19

1. Make sure Git is enabled (menu File → Preferences → Git Enabled) as other have mentioned.
2. Make sure Git is installed and in the PATH (with the correct location, by default: C:\Program Files\Git\cmd) - PATH in System Variables, BTW
3. Change the default terminal. PowerShell can be a bit funny, and I recommend Git Bash, but cmd is fine. This can be done by selecting the terminal dropdown and selecting 'set default shell' and then creating a new terminal with the + button.
4. Restart Visual Studio Code, and sometimes reboot if that fails.

Answer 20

I ran into the same problem after!

How did I fix it?

Step 1: Go to the Settings in Visual Studio Code.

Step 2: Open settings.json.

Step 3: You need to find something like "git.path" in settings.json

Step 4: just add the directory path where Git is installed in your system.

Example: "git.path": "D:/Git/bin/git.exe"

Step 5: Restart your Visual Studio Code.

Answer 21

What worked for me was manually adding the PATH variable in my system.

I followed the instructions from Method 3 in this post:

Fix: ‘git’ is not recognized as an internal or external command

Answer 22

In my case, Git was installed on my Windows 10 OS and there was an entry in PATH variable. But Visual Studio Code 1.52.1 still is unable to detect it from a terminal window, but it was available in a CMD console.

The problem was solved by switching the terminal from PowerShell to CMD or shell, and a Visual Studio Code restart.

Answer 23

Visual Studio Code 1.50 (Sept 2020) adds an interesting alternative with issue 85734:

Support multiple values for the git.path setting

I use VSCode in three different places; my home computer, my work computer, and as a portable version I carry on a drive when I need to use a machine that doesn't have it.

I use an extension to keep my settings synced up between editors, and the only issue I've encountered so far is that the git path doesn't match between any of them.

• On my home machine I have it installed to C of course,
• work likes to be funny and install it on A,
• and for the one on my drive I have a relative path set so that no matter what letter my drive gets, that VSCode can always find git.

I already attempted to use an array myself just to see if it'd work:

"git.path": ["C:\\Program Files\\Git\\bin\\git.exe", "A:\\Git\\bin\\git.exe", "..\\..\\Git\\bin\\git.exe"],

But VSCode reads it as one entire value.

What I'd like is for it to recognize it as an array and then try each path in order until it finds Git or runs out of paths.

This is addressed with PR 85954 and commit c334da1.

---

With Visual Studio Code 1.60+

• "git.enabled": true
• git.path

Answer 24

If you have multiple environments. You could include Git Path in the Visual Studio Code Workspace Setting. For Windows, depending on your setting, you could hit Ctrl + P, search for "settings". Open settings.json (or menu File → Preferences → Settings). Navigate to Workspace Settings. Find "Path" and add paths to Git bin and cmd folders.

Environments can have their own paths. I discovered this when I echoed my PC %PATH% on cmd. Git bin and cmd path where available, but when I was working on my project, echoed %PATH% did not have git and cmd folder. Adding them, as shown above, solved the issue.

Extra Notes:

On cmd, you can echo "%PATH%" and see if git bin and cmd folders are included. If not, you could concatenate using SETX PATH on, for example,

SETX PATH "%PATH%;Path_to_Git_bin;Path_to_Gt_cmd;"

This will make git available on local, root but not in some environments which comes with their own paths (SETX /M PATH "%PATH%;Path_to_Git_bin;Path_to_Gt_cmd;" would have though).

In case you have a long Path that is chopped off due to Path length (getting "Error: Truncated at X characters." message), you can increase the path length in RegEdit.

• In "Search Windows", search for "regedit". Right-click to open as Administrator.
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
• Right-click and modify. Change value data from 0 to 1

This will increase your path length. If it is already one, then I am not sure how to proceed from there :).

[9

Answer 25

For a Linux-based OS: I had such an issue due to a corrupted path, but I was able to temporarily fix the issue and my Git installation was immediately restored.

In case you're facing such path issue type the command below

export PATH="/usr/bin:/bin:$PATH"

Answer 26

Open

C:\Users\nassim\AppData\Roaming\Code\User\settings.json

Comment any Git line there:

// ...
// "git-graph.integratedTerminalShell": "E:\\Apps\\Git\\bin\\bash.exe",
// "git.path": ""
//...

And add git.exe to the OS path.

Note for me: Fixing this Git error also fixed the npm error too. Since they are both defined in the path, if one fail, the remaining will fail as well.

Answer 27

I had this problem after upgrading to macOS v10.15 (Catalina).

The issue is resolved as follows:

1.

Find the Git location from the terminal:

which git

2.

Add the location of Git in settings file with your location:

settings.json

"git.path": "/usr/local/bin/git",

Depending on your platform, the user settings file (settings.json) is located here:

Windows %APPDATA%\Code\User\settings.json

macOS $HOME/Library/Application Support/Code/User/settings.json

Linux $HOME/.config/Code/User/settings.json

Answer 28

Here's what worked for me. Instead of using the Visual Studio Code terminal to run your Git commands, run the Git commands from a cmd terminal at the path of your application.

Answer 29

I found that I had git: false in settings.json and changed it to true. It works now.

Answer 30

First install Git onto your desktop, and then add the encircled extension in Visual Studio Code, as seen in the picture.

That helped me fix the same issue you have.