SourceTree: Updating submodules when pulling from a repository

[Andreas Tietz]

When pulling from a repository containing a newly added submodule, the submodule subdirectory is empty. SourceTree neither updates the submodule contents upon pulling nor do I know how to update manually afterwards from within SourceTree. Currently I'm doing it with "git submodule init" and "git submodule update" on the command line. Is there a way for achieving this from inside SourceTree?

[stevestreeting · Accepted solution]

Hmm, yes this should be happening automatically but it's not, I'll look into it. It definitely works when cloning, and when you change the tracking options, but it seems pulling a new submodule needs some extra handling.

Tracking this one here: https://jira.atlassian.com/browse/SRCTREE-870

[stevestreeting]

FYI this is now fixed for 1.3.2, and I also made SourceTree deal with uninitialised submodules from other sources better too (you can just double-click on an uninitialised submodule and it will update it automatically before opening it).

[Andreas Tietz]

Thanks for your quick reply and fix. Looking forward to working with the new release!

[Coaster3000]

I personally would like a way to manually update a submodule. I can't rely on automatic sometimes as a project is sensitive to another sub project's current code base.

[J Stark]

Is this broken?  When I pull in 3.0.8, I'm not getting submodule updates.  They show up as modified (but can't be discarded).  I have to use another tool to update them.