Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Personalize Git Flow init


When I try to initialise git flow on existant repository from Sourcetree, I can personalise branch names, but these names aren't seem not used by internal init command.

I've got this error (for example, we develop with branch « dev ») :

git init -d 

Using default branch names.

Fatal: Local branch 'develop' does not exist.


Which branch should be used for bringing forth production releases?

   - dev

   - master

Branch name for production releases: [master] 


Which branch should be used for integration of the "next release"?

   - dev

Branch name for "next release" development: [develop] 

Completed with errors, see above


I've try to init git flow from terminal, but I don't have « git-flow » commands or access to « flow » command with git :

Gl0ubI:~$ git-flow
-bash: git-flow: command not found
Gl0ubI:~$ git flow
git: 'flow' is not a git command. See 'git --help'.

Any idea ?


MacOs 10.12.6

Sourcetree 2.7.6 (git embedded 2.17.1 / git-flow embedded)

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 19, 2018


We're looking into reproducing this and will include a fix in a future update. Thank you for the report.

Brian Ganninger
Senior Mac Developer, Sourcetree

"will include a fix in a future update" 
In version 3.2 (224) this has not yet been fixed. 🤔

Version 4.0.1 (234) and still not fixed.

Bug still there. Such a professional team.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events