High We are using different git-flow naming, so when checking out a new projet I always checkout both the "stable" branch (our develop) and the "productive" branch (our master), which I did this time, too. But since 2.7.6 it's failing (might be a little earlier, but not too much earlier, since it worked about a month ago).
Now when trying to initialize git-flow, I get the following error:
git init -d Using default branch names. Fatal: Local branch 'master' does not exist. Which branch should be used for bringing forth production releases? - productive - stable Branch name for production releases: [master] Completed with errors, see above
As you can see, it tries to use the default branch names, although I specified different ones like so:
[SRCTREE-5798] Initializing git-flow with different name for productive branch fails
@stan.derksen I know, but it's still better than manually creating a "develop" branch, hoping the implemented "git-flow" works, and then manually changing the config file to match the branches that are actually used... given the time this issue has been reported, and no update since then, I will gladly take a "git-flow init" terminal command over the above.
Use Sourcetree's integrated terminal:
Last login: Tue Oct 10 11:01:57 on console user@user-iMac ~ % cd /Users/user/project-name user@user-iMac project-name % git-flow init Which branch should be used for integration of the "next release"? - staging - feature/awesome-feature Branch name for "next release" development: [] staging How to name your supporting branch prefixes? Feature branches? [feature/] Release branches? [release/] Hotfix branches? [hotfix/] Support branches? [support/] Version tag prefix? [] user@user-iMac project-name %
You can then use git-flow from Sourcetree normally
Just ran into this. And, `git flow init` in Terminal doesn't work for me. It looks like I don't have `git flow` installed.
For now, I will just keep doing things by hand.
Reproduced with version 4.0.1 in MacOS 10.15.4.
The workaround as told is running the `git flow init` command in the Terminal.
same to me! thank you! i fixed it by 'git flow init' thank you Dominique Pijenburg and Evgeny
Fix available in version 4.2.6. Kindly upgrade to latest version.