Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.79.0-insider OS Version: macOS 13.3.1 Steps to Reproduce: VSCode in a computer with a relatively old version of Git (2.16.2 does it). a project under version control. control fails silently and only shows the Publish button. Trying to publish causes an error. This seems to be related to a change that makes use of the option in , which doesn't seem to be supported by old-ish Git.
sorry about this. I will try to get this fixed this week.
I am also experiencing the same issue. VS Code Version: 1.79.0-insider OS: Windows_NT x64 10.0. git version 2.17.1
It looks like the option was in git 2.18.0. Ideally you would want to keep your git installation up to date to keep up with the security fixes. Having said that I do understand that there are scenarios in which one cannot install the latest git release, so I have pushed a fix for this issue. The fix will be included in the next Insiders release.
Thanks a lot! I agree with keeping git up to date. Unfortunately I use VSCode with the remote extension in many servers where I don't have control of what version of Git is installed, so having at least some basic Git functionality there is much appreciated.
Hi, I encountered the same issue with my VSCode + WSL1 (I haven't upgraded to WSL2 for some reason) git version: 2.11.0 VSCode Version: 1.79.0
could you please share the complete contents of the ? What version of git are you running inside WSL? This flag should only be in case you have a version of git that support it.
Same issue here
Affecting me too. This seems like a major breaking change. Is there a bugfix release planned? Thanks.
could you please share more about your environment? What version of git are you running (git --version). Are you also using WSL, or any other remote environments? Anything that helps me reproduce the issue would be extremely valuable (ex: the contents of ). Thanks!
Thanks Ladislau Using git 2.17. I don't want to upgrade to insiders build Get Outlook for iOS
could you please run and share the exact output. My current hypothesis is that for some reason we are unable to correctly detect the version number and that is why we incorrectly add the flag.
Let's continue the investigation in this issue Thanks!

Discussion:
args.push('--ignore-submodules'); } <del> if (opts?.similarityThreshold) { </del> <ins> // --find-renames option is only available starting with git 2.18.0 if (opts?.similarityThreshold && this._git.compareGitVersionTo('2.18.0') !== -1) { </ins> args.push(`--find-renames=${opts.similarityThreshold}%`); }