2026/6/4 -Updating a Git submodule to the latest commit point (the latest version of the submodule repository) is straightforward. Go inside the submodule folder.
2026/1/30 -I have an extremely weird issue with git. I have never seen it before, none of my coworkers have seen it before, but it's reproducible on my PC. The setup:.
2026/3/20 -A Git submodule is a reference to another Git repository at a specific commit, embedded inside a parent repository. Think of it as a pointer - your parent repo ...
2026/9/9 -The init and update subcommands of git submodule will maintain submodules checked out and at an appropriate revision in your working tree. Alternatively you can ...
2026/2/5 -I just learned about a helpful git command option and configuration setting to avoid this fiasco. First, you can use two options: git push --recurse ...
2026/5/2 -After adding a submodule, you can go to the submodule directory deps/back and then switch to a specific commit or tag. Then, go back to the parent project ...
2026/4/7 -Git submodules allow one repository to reference another at a specific commit, enabling dependency management without merging codebases.
2026/7/24 -A common misconception: a submodule tracks a branch. In reality, the superproject records a specific commit SHA for each submodule.
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/1/20 -We have a setup like that, each submodule is its own bitbucket repo with its own PRs. I don't think bitbucket lets you do a single PR that spans multiple repos.