#Git submodule specific branch how to
#Git submodule specific branch update

#Git submodule specific branch how to

If you have been following the previous guides, and other materials, you should have a clearer understanding of what Git is, what it does, how to use it best, and how to troubleshoot. 2ġThere is ongoing work in Git to make submodules more aware that they are submodules, to help fix items like footnote 2.ĢThis is pretty dangerous, so we don't normally want it, but: what happens, for instance, if path/to/X in commit a1234567 is the submodule, but path/to/X in commit b789abc is a plain file? Git tries hard not to destroy the submodule (or its clone)-these days, the submodule repository proper gets moved to a. Here, we will be covering two more major features that Git has to offer: tags and sub-modules. Basically it is the Git default that a submodule is pegged to a specific hash (i.e. and want to treat the aggregated whole as a single project from then on. A git submodule is a record within a host git repository that points to a specific commit in another external repository.

#Git submodule specific branch update

What makes this Git repository be a submodule is that once you exit out of it back to the superproject, certain Git commands in that superproject will run: (cd submodule & git checkout $hash)Īs a result, after you have made changes in a submodule's working tree, it's a good idea to get them committed and then git push-ed elsewhere, lest the superproject do something crazy like run git checkout, or really crazy like remove the submodule entirely. Options -remote, Instead of using the superprojects recorded SHA-1 to update the submodule, use the status of the submodules remote-tracking branch -N, -. git submodule -quiet foreach -recursive git submodule -quiet.

Remember that-at least for now 1-a submodule doesn't really 'know' that it is a submodule, so once you cd into it and start running Git commands ( git checkout, git add, and so on), you're just working in an ordinary Git repository.