Fetch submodules automatically

77 votes

Currently with release 7.6.1 if repository uses submodules, there is an inevitability to open each submodule before updating main repository ( fast forward, checkout ).

It sometimes is tiring, especially when repository uses few submodules, and their submodules uses also submodules. Without opening submodule, updating it does nothing.

Under consideration Quality of Life Suggested by: Szymon (01 Jul, '21) • Upvoted: 21 Mar • Comments: 7

Comments: 7

28 Jul, '21
ke
yes!!! I've being troubling with this for weeks!!! please let there be a swith botton to manage it!
16 Feb, '22
Axel Heider
Please add this feature together with an option to enable or disable this feature (see also https://feedback.gitkraken.com/suggestions/193513). Having an option to fetch submdules on demand to get all update would also be helpful. And the whole thing should work recursively in case there are sub-submodules.
24 Sep, '22
Ivan
please do something, I love gitkraken but this is very time consuming when dealing with many nested submodules & it makes rebases a nightmare....
04 Jan, '23
Fabrizio
If I have understood correctly we are talking about sub-submodules.
I fully agree that GitKraken seems forgetting that a sub-module can have on its own also submodules.
I could agree that is not really common, nevertheless submodules nesting happens... and it's normal!
When switching branch or perform any operation that involves sub-sub-modules we need to open a prompt to issue a "git submodule ..." to fix what is left partially done by GitKraken. Really error-prone and not justified.
I really encourage the GitKraken team to consider that submodules can be nested and take this fact into consideration on any operation to be performed consistently.
Thanks!
14 Feb, '23
Axel Heider
My workaround for this is running `git submodule update --init --recursive --jobs 16` in the command line. In you case `git fetch --recurse-submodules --jobs 16` should also work.
21 Feb, '23
Yoshua Nava
This feature goes in the same direction as https://feedback.gitkraken.com/suggestions/354160/pull-all-submodules-in-a-workspace#comment482078, and I think it would improve the experience when working with submodules significantly.

:pray: Please :pray:
17 Mar, '23
MKL
I second that, because that it the reason I keep Git Extensions installed, just for pulling and initializing correctly all submodules. It is especially annoying when doing a rebase, when the branch is using a tag on a submodule that was not locally fetch. You end up with a ton of errors, and to avoid it, you need to open each submodule and fetch.