Why does Sourcetree Git detach branch on merge conflict?

One member of my team has a problem that none of the rest of the team has. It is as follows:

  • They commit some work to local develop (ok)
  • They pull from remote develop (ok)
  • They get a merge conflict (ok)
  • They end up on a detached branch (i.e. none of their local branches are selected) and cannot resolve the conflict and commit back to develop. Attempting to change back to develop warns that a rebase is in progress (Not ok)

I assume it must be a setting or config that causes this as none of the rest of the team, on the same version and hardware, experience this. What the rest of us find that after a merge conflict we remain on the same local branch. Has anyone come across this before and know how to resolve it?

2 answers

Never had that happen to me. Is he using the latest version of SourceTree? Is he using Embedded Git or System Git (installed separately)?

He's using the folllowing: - SourceTree v 2.0.1 - Embedded Git v 1.8.4.2

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Brian Ganninger
Published Jan 23, 2018 in Sourcetree

Tip from the team: workflow and keyboard shortcuts

Supported Platforms macOS Sourcetree has a lot to offer and, like many developer tools, finding and using it all can be a challenge, especially for a new user. Everyone might not love ...

649 views 0 4
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you