I have a repository with few branches and submodules. Submodules have branches of their own. On each branch of the main repository I use a particular branch of the corresponding submodule. The SourceTree correctly tracks subbodule commits from the active branch.
However, the active submodule branch which corresponds to a given main repository branch is not always being handled by the SourceTree. When I switch main repository branches and then open submodules, SourceTree doesn't know which active branch that submodule is on even though it correctly displays the active commit. I have to explicitly put submodule on the correct branch through SourceTree GUI.
This behavior results in erroneous pull/push request from/to the submodule branches when someone forgets to explicitly put submodule on the correct branch.
It should be possible to set submodule to a correct active branch when it is open. Is this an issue with the SourceTree?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.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