2026/9/6 -Every developer hits this at least once. Submodules always check out in detached HEAD state. They're pinned to a specific commit, not a branch. If you make ...
2026/9/1 -Put two worktrees on different superproject branches and they reference the same submodule at two different commits. Each needs its own submodule checkout ...
2026/9/9 -The checkout will fail if there are uncommitted changes to any files where <branch> and your current commit have different content. Uncommitted changes will ...
2026/10/1 -A modified submodule in git status means the nested repository is at a different commit than the parent recorded, or it has uncommitted changes. Add and clone.
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/6 -You can still use the same gitlink in the parent repo representing it's commit id and git will still manage it. ... Then you cd out and commit the submodule hash ...
2026/10/12 -A possible fix: after rebasing each branch, run git submodule update for submodules whose checkout matched their pin before that branch was rebased. Those are ...
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/5 -The checkout will fail if there are uncommitted changes to any files where <branch> and your current commit have different content. Uncommitted changes will ...
2026/9/9 -The submodule's working directory is removed from the file system, but the Git directory is kept around as it to make it possible to checkout past commits ...