As mentioned in my previous answer to git submodule update, that command checks out the specific version of the project, base on their .gitmodules file. The GitPro page does insist: This is an important point with submodules: you record them as the exact commit they’re at. You can see which commit is referenced by running … Read more
You should just be able to edit the .gitmodules file to update the URL and then run git submodule sync –recursive to reflect that change to the superproject and your working copy. Then you need to go to the .git/modules/path_to_submodule dir and change its config file to update git path. If repo history is different … Read more
Edit (2020.12.28): GitHub change default master branch to main branch since October 2020. See https://github.com/github/renaming This answer below still reflect the old naming convention. Update March 2013 Git 1.8.2 added the possibility to track branches. “git submodule” started learning a new mode to integrate with the tip of the remote branch (as opposed to integrating … Read more
This GitPro page does summarize the consequence of a git submodule update nicely When you run git submodule update, it checks out the specific version of the project, but not within a branch. This is called having a detached head — it means the HEAD file points directly to a commit, not to a symbolic … Read more
Note: Git 1.8.2 added the possibility to track branches. See some of the answers below. It’s a little confusing to get used to this, but submodules are not on a branch. They are, like you say, just a pointer to a particular commit of the submodule’s repository. This means, when someone else checks out your … Read more
Git still think mysubmodule is a submodule, because it is recorded in the index with a special mode “160000”. See “git submodule update needed only initially?” for more. To check that, as in in this answer, you can do a: $ git ls-tree HEAD mysubmodule 160000 commit c0f065504bb0e8cfa2b107e975bb9dc5a34b0398 mysubmodule That doesn’t depend on the presence … Read more
If it’s the first time you check-out a repo you need to use –init first: git submodule update –init –recursive For git 1.8.2 or above, the option –remote was added to support updating to latest tips of remote branches: git submodule update –recursive –remote This has the added benefit of respecting any “non default” branches … Read more
With version 2.13 of Git and later, –recurse-submodules can be used instead of –recursive: git clone –recurse-submodules -j8 git://github.com/foo/bar.git cd bar Editor’s note: -j8 is an optional performance optimization that became available in version 2.8, and fetches up to 8 submodules at a time in parallel — see man git-clone. With version 1.9 of Git … Read more
How do I remove a submodule?