Skip to content
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

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

Open
gerardwolf opened this issue May 16, 2019 · 10 comments

Comments

@gerardwolf
Copy link

"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

@andrea5586
Copy link

andrea5586 commented Sep 17, 2019

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!

@jwtd
Copy link

jwtd commented Jan 19, 2020

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.

@ruffcoins
Copy link

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.

@anhthang
Copy link

@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

@andrea5586
Copy link

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

@SolutiFelipe
Copy link

SolutiFelipe commented Mar 17, 2021

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

@gangadharreddybandi
Copy link

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.

@neliomarcelino
Copy link

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.

@jerembdn
Copy link

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.

@adventuretocode
Copy link

@here Git branch names should not allow white spaces,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants