vscode-gitflow icon indicating copy to clipboard operation
vscode-gitflow copied to clipboard

"git.exe returned status 128" issue when trying to initialise gitflow using 'Initialize repository for gitflow'

Open gerardwolf opened this issue 6 years ago • 10 comments
trafficstars

"git.exe returned status 128" issue when trying to initialise gitflow using 'Initialize repository for gitflow' It's a brand new Surface Laptop 2 running Windows 10 with a fresh installation of VS Code (v1.33.1) and Git (2.21.0). I can confirm that git has been set up correctly as I can use normal git functions without issue from within VS Code, just not the extension functionality. Be awesome if you help.

image

gerardwolf avatar May 16 '19 04:05 gerardwolf

Had the same issue a couple of minutes ago with this setting: Win10 git version 2.19.2.windows.1, vscode version 1.38.1

I was working with a workspace with two folders: one had an already initialized gitflow and the second (in order) with the repo i wanted to initialize. Same error "git.exe returned status 128".

I opened the folder i wanted to initialize in a new VSCode instance and then i performed git init. At that point i performed Initialized repository for gitflow and everything worked.

Hope this helps!

andrea5586 avatar Sep 17 '19 19:09 andrea5586

I'm experiencing this issue as well. The resolution described above did not resolve the issue for me.

git version 2.21.0 Visual Studio Code v1.41.1 Gitflow ext v1.2.1 Repo is clone from bitbucket.

jwtd avatar Jan 19 '20 15:01 jwtd

I had the same problem also. With the help of @andrea5586 I removed one of the folders in my workspace that I wasn't using. it solved my error.

ruffcoins avatar May 01 '20 20:05 ruffcoins

@Anthonynzube I think the issue due to the current version still not support for workspace. I have updated and published new gitflow extension, pls try and let me know if you still got the error

anhthang avatar May 11 '20 10:05 anhthang

Good to know! @buianhthang thank you for the update. I will give it a try and let you know of there are any issues!

andrea5586 avatar May 11 '20 14:05 andrea5586

Guys, I had the same problem and solved it just by opening the folder, whose I wanted to start Gitflow, through the terminal with the command code ./my/project/dir

SolutiFelipe avatar Mar 17 '21 14:03 SolutiFelipe

Had the same issue a couple of minutes ago with this setting: Win10 git version 2.19.2.windows.1, vscode version 1.38.1

I was working with a workspace with two folders: one had an already initialized gitflow and the second (in order) with the repo i wanted to initialize. Same error "git.exe returned status 128".

I opened the folder i wanted to initialize in a new VSCode instance and then i performed git init. At that point i performed Initialized repository for gitflow and everything worked.

Hope this helps!

I had the same issue and I tried this solution and it worked.

gangadharreddybandi avatar Aug 13 '21 14:08 gangadharreddybandi

I also had this "status 128" but the problem was the spaces on the name of the new feature. The name of the new feature need to be without any spaces. Used '-' in my case.

neliomarcelino avatar Aug 30 '21 10:08 neliomarcelino

I had this issue too because the VSC workspace i worked on have multiple git repos. Open the project containing the git repo worked for me.

jerembdn avatar Sep 21 '22 17:09 jerembdn

@here Git branch names should not allow white spaces,

adventuretocode avatar Aug 06 '24 12:08 adventuretocode