Git submodule update

by

I’m not clear on what the following means (from the Git submodule update documentation):

…will make the submodules HEAD be detached, unless --rebase or --merge is specified…

How does --rebase/--merge change things?

My main use case is to have a bunch of central repositories, which I will embed via submodules into other repositories. I would like to be able to improve on these central repositories, either directly in their original location, or from within their embedding repositories (the ones that use them via submodule).

  • From within these submodules, can I create branches/modifications and use push/pull just like I would in regular repositories, or are there things to be cautious about?
  • How would I advance the submodule referenced commit from say (tagged) 1.0 to 1.1 (even though the head of the original repository is already at 2.0), or pick which branch’s commit is used at all?

4 Answers
4

Leave a Comment