[Enhancement] Submodule options

[idamachmadfaizin]

The submodule options to not auto-update recursively.
Maybe we can add another options, so the developer have full control to submodules.

[love-linger]

Thanks to your reminder, I found that there is an unreasonable aspect in the function of updating submodules in SourceGit currently.

Although we provide the Traverse submodules recursively option in the Update Submodules popup, this option is basically useless. Because after checkout/merge/pull, when automatically updating the initialized submodules, the --recursive option is always applied.

Moreover, when automatically updating submodules, SourceGit can hardly detect scenarios where the --recursive option should not be used. After referring to some other mature git clients, I decided to always enable the --recursive option when initializing and updating submodules.

[cdammanintopix]

What about a global setting that enables --recursive or not?

[love-linger]

What about a global setting that enables --recursive or not?

I think that even if this setting is added, it should be in the repository settings rather than globally.

[idamachmadfaizin]

I understand the reason behind the --recursive option, and it is indeed useful when cloning the project for the first time.

However, when we are actively switching branches during development, I believe as developer we should have more control. For example, some submodules should always remain on the main branch instead of automatically following the parent repository’s branch changes.

This approach helps avoid unexpected submodule state changes and makes the development workflow more predictable and stable.