Let’s say I want to include a library’s source code in my project, but I don’t want to use it as is. Let’s translate the above scenario to something that might happen in development. By using the Room as a submodule, I can do whatever I want to my Room without having it affect my House. Using the above as an example, the Room repository depends on the House repository, but they operate separately. Now that we’ve created a Git submodule, let’s answer the question: Why? Why do we use Git submodules in the first place? In most cases, Git submodules are used when your project becomes more complex, and while your project depends on the main Git repository, you might want to keep their change history separate. Url = /Room.git Why do we use submodules? If we look into the file, we’ll see something like this: gitmodules -This is the configuration file that shows how your project is mapped. If you do a git status, you will now notice two things: lib/Room, the path to the submodule, as well as a new file called.
ADD A GIT SUBMODULE UPDATE
After initialization, you’ll need to update your submodule to pull the contents and latest updates from its repository with the command: git submodule update. In order to fill the submodule with the contents of the submodule’s repository, the submodule must be initialized with: git submodule init.
When you first add a submodule, you may not see anything inside the subfolder, depending on your Git version. If we look into the House repository, we’ll see the subdirectory Room repository like so: If a path is not provided, the submodule will default to the same name as its repository. lib/Room – the path where the submodule repository will be added to in the House repository (optional)./Room.git – the repository that is going to be added as a submodule.git submodule add – the syntax to add a Git submodule.To do so, you would use the command git submodule add with the absolute or relative URL of the project you want to add as a submodule. Let’s say we want to add a submodule called Room under the House repository. How do you use a Git submodule? First, let’s create one under a repository called House. This allows you to be able to set your subdirectory to refer to a specific commit you may want to work with.
The subdirectory repository will have its own Git system, which means it will have its own commits history, independent from your main repository. Before we begin, let me explain what a Git submodule is.Ī Git submodule is a git tool that allows a user to essentially add a Git repository as a subdirectory of another Git repository. Many developers already use Git to manage their codebase, but what about Git submodules? How do you use them and why? In this post, I will provide a basic tutorial on creating one, as well as explain why you would use a Git submodule in the first place.
0 kommentar(er)
