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?
Regards,
Eugene
Brian,
Is anyone at Altassian looking into this? This bug causes a lot of issues in our daily work! When switching between main repository branches SourceTree messes up the project content when submodules have local branches.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Which OS and version of SourceTree are you running?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.