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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,673
Community Members
 
Community Events
176
Community Groups

SourceTree GitFlow keeps asking to finish feature

Edited

I am using SourceTree v3.0.8 in Windows.  In SourceTree, when my current branch is 'develop' and I click on Git-flow in the toolbar, the pop-up dialog thinks develop is a feature branch and offers only to either 'Finish Feature' or 'Other Action' (ie, it doesn't offer to 'Start New Feature').

If I then click on 'Finish Feature', it pops up the Finish Feature dialog box with 'develop' in the Feature Name dropdown.  If I wait a few seconds, 'develop' disappears from the dropdown and the 'OK' button becomes disabled.  If I click on the Feature Name dropdown, the list is completely blank.

It seems to me that some configuration file is wrong, but I have no idea where or what that file may be.

Any suggestions?  Thank you in advance.

1 answer

1 accepted

7 votes
Answer accepted

Actually, shortly after posting the question, I have found the problem (it appears that it could be a bug in SourceTree in initializing GitFlow).

I looked at the .git/config file in my project and the '[gitflow "prefix"] section was as follows:

[gitflow "prefix"]
feature =
bugfix =
release =
hotfix =
support =
versiontag =

I then looked at the .git/config file in another project where Git Flow is working properly and that file was as follows:

[gitflow "prefix"]
feature = feature/
bugfix = bugfix/
release = release/
hotfix = hotfix/
support = support/
versiontag =

When I copied that section over the top of the section in the config file in the project where Git Flow wasn't working, that fixed the problem.

So it seems that there may be a bug in SourceTree where it doesn't properly initialize gitflow in the config file.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events