Git flow bug in SourceTree 3.0.17? - two clones of same repository report same gitflow status

[adlanwastaken]

I have a repository hosted in Bitbucket Server.  I have cloned this to my local machine and have initialized Git Flow using Sourcetree v3.0.17 (System Git v 2.21).  On this first repository, I have started a feature branch using Sourcetree's built in Gitflow button.   Currently in this working copy I have the feature branch checked out. 

I then cloned the same repository to a different location using Sourcetree, and also initialized GitFlow on the second working copy.  After initializing Gitflow on this copy (using the default names for branches as I had done with the first), the GitFlow button on the second repository shows the recommended actions as 'Finish Feature' with the Feature name reported as "Develop".  

[minnsey]

Hi

Can I check have you committed and pushed anything to the Bitbucket Server since initializing Git-Flow on either clone?

I'm not sure I understand why you init-ed twice. 

[adlanwastaken]

I am only init-ing twice as I am being prompted to on the second repository.

I have pushed from the original clone of my repository since checking out (and since initializing Git-Flow).  I have also used Git-Flow on this clone multiple times to create and complete feature branches, hotfixes etc. and pushed the changes afterwards. 

If I check out a new copy and then attempt to use Git Flow in SourceTree, it prompts me to initialize again.  Do I take it from your comment that the GitFlow configuration should have been pushed to Bitbucket server somehow?  If this be the case, can I check the .gitignore file for something that shouldn't have been included?

Thanks Andrew.