One member of my team has a problem that none of the rest of the team has. It is as follows:
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?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
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!
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