It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Missing Start Feature right after Gitflow init

When Gitflows in the new repository is initialized via Sourcetree (3.1.2), on one computer it doesn't offer Start Feature, but Finish Feature option. If the Start Feature is selected from Other Actions dialog, it seems to be working, but the status of the repository is somehow affected. This feature branch cannot be merged. And also other starting/finishing operations (e.g. start Release) are confused.

Everything works correctly on another computer. Is there any Gitflow status which could be somehow reset?

Win 10 64-bit, Git 2.21

1 answer

0 votes
minnsey Atlassian Team Mar 22, 2019


Is it possible the git-flow state was already committed and then pull from another user?

You can see what git-flows underlying view of the state of the repository from the command like, e.g.

>Git flow feature list

etc see

Sourcetree will show options depending on what it sees as the current state of the repository, I.e. if it believes the current branch is an open feature then the options it shows by default will be those to do with completing that feature.

Is that repository on that workstation on a feature branch?

minnsey Atlassian Team Mar 22, 2019

FWIW When clicking the Git-Flow button Sourcetree should be comparing the name of the current branch against the various prefixes, hotfix/, feature/ etc and then using that match or lack of it to decide what options to show.

So far we've only been able to reproduce this with Git 2.21.0, potentially it is a change it that. Can you confirm that it works with Git < 2.21.0 ?

I'm currently using the System Git version 2.21.0/LibGit2Sharp 0.25.4 + git-lfs v2.7.1. If I switch to the embedded version, which is 2.20.1/LibGit2Sharp 0.25.4 + git-lfs v2.6.1, then the Finish Hotfix menu action appears. I haven't tried it yet, because I haven't finished the hotfix yet, but just the fact that it is there now when it wasn't before gives me a bit of confidence.

I can confirm it works fine if Git is downgraded to 2.20 version (embedded one). It is indeed the only difference between both computers.

minnsey Atlassian Team Mar 25, 2019

Thanks for confirming, we are continuing to investigate. 

minnsey Atlassian Team Mar 25, 2019

It looks like an update to fix this should be on its way via Git for Windows

Like Jan Tošovský likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Sourcetree

Sourcetree for Windows - CVE-2019-11582 - Remote Code Execution vulnerability

A vulnerability has been published today in regards to Sourcetree for Windows.  The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...

4,962 views 0 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you