-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
2.4.7.0
-
None
-
Severity 3 - Minor
When a merge results in a conflict in a submodule, then this submodule is not shown in left pane. I used the submodule in the left pane to navigate to submodule with the conflict to resolve the conflict. Now I have to open the submodule by opening a new tab and then I can either use a bookmark or I have to look for submodule on my system.
Is the conflict in the .gitmodules file itself, i.e. does it now contain <<<<< entries?
If so the upcoming 2.5 release should improve the error handling in this situation, by flagging up the corrupt .gitmodules file, but ntil the file is fixed git can't parse it, so Sourcetree can't display its contents.