git-submodules

I’m afraid the URL for submodules always just points to the repository – you can’t specify that you only want a subfolder of a repository, in the same way that git doesn’t support “narrow clones” in general. If you can’t live with having the whole repository as a submodule, you could always create a new … Read more

When you want to pull a specific new module, you can use the following command: git submodule update –init local/path/to/submodule/folder If you wish to initialize all new submodules however. you can omit the path to the folder like so: git submodule update –init

Git is doing exactly what it’s supposed to be doing. git submodule update will set your submodule to what the current commit in the parent repo specifies the submodule should be at. This way you can checkout another branch, older commit or tag, then run git submodule update and the submodule will be set to … Read more

Does ../extern/Lib1 refer to a Git repository? If it does not, Git wouldn’t know how to had the Git repo url to its .gitmodule Also, try: with the destination lib not already existing (even empty) with an absolute path instead of a relative path (you can use a relative one, but just in case, it … Read more

You don’t need a seperate clone. The sub-module folder is a world of its own. Just edit, commit, branch, and push to your heart’s delight. Git is great that way. 🙂 BTW, the parent repository will even detect when changes happen inside the sub-module folder and offer you to commit the current state of the … Read more

Setting up shared dependencies as submodules is easy. The git submodule command doesn’t do it automatically, but a submodule is nothing more than a nested repository — and git doesn’t require any actual repository or its worktree to be in any particular place. Set up a libraryXYZ repo for use as a shared submodule # … Read more