Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Git-Flow not working after latest Sourcetree update

mh-RAV
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 21, 2025

After the latest Sourcetree update, a message appeared prompting us to update Git due to changes with Git-Flow, as described here: https://support.atlassian.com/sourcetree/kb/unbundle-git-lfs-and-git-flow-dependencies-in-sourcetree/

We followed the instructions and updated Git. However, we are using Microsoft’s Git version with VFS support: https://github.com/microsoft/git

In Sourcetree, we have configured it to use the system Git version.

Now, when we are on a branch where Git-Flow is enabled, we receive a message saying that we need to update to Git 2.6.4 or later, with a recommendation to use 2.51.0.1. We are already using Microsoft Git version 2.51.1, which is newer than the recommended one.

How can we get Git-Flow working again? Do we need to wait for a bug fix, or is there a workaround?

2 answers

1 accepted

2 votes
Answer accepted
Tim Wright
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 21, 2025

We have the same issue, our MDM has forced our team onto 2.51.1 and we've had to roll back a version to use git-flow. It is a workaround but not an ideal situation.

To get the previous version direct from git-scm you can copy the download link and edit the version number.

mh-RAV
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 21, 2025

Thanks for the Info, the revert to 2.51.0.vfs.0.3 worked. But this should still be addressed by Atlassian. Have marked this as the answer for now.

0 votes
Tomislav Tobijas
Community Champion
October 21, 2025

Hey guys,

You could check if there are any open bugs related to this here. I believe that for Sourcetree, you can even create a new ticket by yourself 👀 (if you do, feel free to share the link of the bug here)

Cheers,
Tobi

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events