Git Submodules
This page is maintained by Kirill Nedostoev
Eventually, any interesting software project will come to depend on another project, library, or framework. Git provides submodules to help with this. Submodules allow you to include or embed one or more repositories as a sub-folder inside another repository.
To add a new submodule you use the git submodule add command with the URL of the project you would like to start tracking.
For example, you would add traces as a submodule of mipt-mips. In the mipt-mips repository:
git submodule add https://github.com/<user>/traces
By default, submodules will add the subproject into a directory named the same as the repository, in this case traces.
If everything looks good, you can commit this change and you'll have a traces folder in the mipt-mips repository with all the content from the traces repository.
On GitHub, the traces folder icon will have a little indicator showing that it is a submodule:
You're a new collaborator joining Project mipt-mips. You'd start by running git clone to download the contents of the mipt-mips repository. At this point, if you were to peek inside the traces folder, you'd see nothing.
If you're cloning mipt-mips for the first time, you can use a modified clone command to ensure you download everything, including any submodules:
git clone --recursive <project url>
or use
git submodule init
git submodule update
If you want to check for new work in a submodule, you can go into the directory and run git fetch and git merge the upstream branch to update the local code.
Now if you go back into the main project and run
git diff --submodule
you can see that the submodule was updated and get a list of commits that were added to it.
There is an easier way to do this as well, if you prefer to not manually fetch and merge in the subdirectory. If you run
git submodule update --remote
Git will go into your submodules and fetch and update for you.
It’s quite likely that if you’re using submodules, you’re doing so because you really want to work on the code in the submodule at the same time as you’re working on the code in the main project. So now let’s go through an example of making changes to the submodule at the same time as the main project and committing and publishing those changes at the same time. You should:
git submodule update --remote --merge
If we go into the main directory, we have the new changes already merged into our local branch.
Now we have some changes in our submodule directory. Some of these were brought in from upstream by our updates and others were made locally and aren’t available to anyone else yet as we haven’t pushed them yet. You should:
git push --recurse-submodules=on-demand
or cdto the path and use
git push
Often your submodule needs to be upgraded to a new release version. It is very simple to do this.
We'll look at an example of the binutils update. With the googletest and the rest of the submodules, everything is absolutely the same.
At first, you should cd to the path and use
cd binutils/
git fetch
git log
git checkout <commit>
Yot use git log to find needed commit. After it, you should commitchanges:
cd ..
git add binutils/
git commit -m "<message>"
git push