2026/9/6 -Submodules always check out in detached HEAD state. They're pinned to a specific commit, not a branch.
2026/10/1 -A Git submodule embeds another repository inside yours at a specific commit, The fix is to check out a branch before working in a submodule. The order is ...
2026/9/9 -Git directory is kept around as it to make it possible to checkout past commits without requiring fetching from another repository.
2026/11/2 -Git clones the main repository, then clones every submodule and checks out the commit the main repository points to. Nested submodules (submodules inside ...
2026/9/1 -The gitlink records only which commit to check out, so .gitmodules carries a url per submodule and update clones from there, which is the only resolution ...
2026/9/28 -If --force is specified, the submodule will be checked out (using git checkout --force), even if the commit specified in the index of the containing repository ...
2026/10/13 -Submodule pointers are bookmarks Git records a specific commit for every submodule. In a repository that builds from submodules, those pointers are critical.
2026/10/21 -The --recurse-submodules flag tells Git to also clone all nested repositories and check out the correct commits.
2026/11/10 -This option is only valid for the update command. --checkout. Checkout the commit recorded in the superproject on a detached HEAD in the submodule. This ...
2026/9/9 -We can use CMake's support for external projects together with the Git submodule functionality to fetch, compile, and link source code from external ...