Where is gitmodules file

Just that I cannot find the. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. No submodule mapping found in. Asked 8 years, 5 months ago.

Active 1 year, 8 months ago. Viewed 56k times. When I run git submodule init , I get the following error: No submodule mapping found in. Improve this question. Community Bot 1 1 1 silver badge. Kim Stacks Kim Stacks I think it might be worth noting that you can create a submodule accidentally if you git init a new repo inside of an existing repo the definition of a "submodule".

If you do this, the. Add a comment. It is necessary to go into the submodule and checkout the desired branch, make your commits, and then push. Then you can point the main repository to the new submodule commits. Additionally you may emphasize the importance of pushing the submodule code as well as pointing the main repo to it.

For example, if you commit to the submodule without pushing and point the main repo to those commits, you'll be in trouble because others won't have the submodule commits that your main repo is now pointing to. Can we give path for submodule to any absolute path, which means outside the parent git repository? Is there any option to add submodules to any desired path outside the parent git repository folder?

Can I make the submodule contains only certain folders in my repository? Remove it from the modules folder. You can also do this from a UI file explorer of some type: rm -rf.

When you add a submodule in Git, you don't add the code of the submodule to the main repository. Upon running git submodule add command, the submodule's code is added to the repository.

What prevents for a submodule to be updated is the. This won't pull the code. What git submodule init command does is initalizing the local git configuration with the submodules list, retrieved from the.

Still no submodule's code is present. The whole section is wrong. There is a conflation between commit and push git workflows and wrong use of the git add command. This is not automatically done by git pull, because with git pull it only retrieves the information that the submodule is pointing to another commit.

The submodule can be updated by using git pull inside the submodule's directory. This won't update the submodules, what it will do is 1 initialize the git configuration with the submodules list retrieved from the.

The text contains some mistakes, see hsaih reply for this. After you commit and push, to get the submodule to update new content from the other repo, there's the magic command:. I have a repo that uses as submodule a repo from another Git provider, but the link doesn't work. Do you why? For anyone who's getting issues with cloning. Indeed zhl , thanks for the feedback :. Skip to content. Sign in Sign up.

Instantly share code, notes, and snippets. Last active Nov 13, Code Revisions 33 Stars Forks Embed What would you like to do? Embed Embed this gist in your website. Share Copy sharable link for this gist. Learn more about clone URLs. Download ZIP.

Git Submodules basic explanation. Git Submodules basic explanation Why submodules? A couple of advantages of using submodules: You can separate the code into different repositories. You can add the submodule to multiple repositories.

Basics When you add a submodule in Git, you don't add the code of the submodule to the main repository, you only add information about the submodule that is added to the main repository. Adding a submodule You can add a submodule to a repository like this: git submodule add git github.

Getting the submodule's code If a new submodule is created by one person, the other people in the team need to initiate this submodule. Then you'll have to initiate them with: git submodule init This will pull all the code from the submodule and place it in the directory that it's configured to. Pushing updates in the submodule The submodule is just a separate repository.

Git submodules enable a Git repository to incorporate and track version history of external code. Often a code repository will depend upon external code. This external code can be incorporated in a few different ways. The external code can be directly copied and pasted into the main repository. This method has the downside of losing any upstream changes to the external repository. Another method of incorporating external code is through the use of a language's package management system like Ruby Gems or NPM.

This method has the downside of requiring installation and version management at all places the origin code is deployed. Both of these suggested incorporation methods do not enable tracking edits and changes to the external repository. A git submodule is a record within a host git repository that points to a specific commit in another external repository.

Submodules are very static and only track specific commits. Submodules do not track git refs or branches and are not automatically updated when the host repository is updated. When adding a submodule to a repository a new. If the host repository has multiple submodules, the. If you need to maintain a strict version management over your external dependencies, it can make sense to use git submodules.

The following are a few best use cases for git submodules. The git submodule add is used to add a new submodule to an existing repository. The following is an example that creates an empty repo and explores git submodules. This sequence of commands will create a new directory git-submodule-demo , enter that directory, and initialize it as a new repository. Next we will add a submodule to this fresh new repo.

The git submodule add command takes a URL parameter that points to a git repository. Here we have added the awesomelibrary as a submodule. Git will immediately clone the submodule.

We can now review the current state of the repository using git status There are now two new files in the repository. Looking at the contents of. The default behavior of git submodule init is to copy the mapping from the. This may seem redundant and lead to questioning git submodule init usefulness. This enables a workflow of activating only specific submodules that are needed for work on the repository. This can be helpful if there are many submodules in a repo but they don't all need to be fetched for work you are doing.

Once submodules are properly initialized and updated within a parent repository they can be utilized exactly like stand-alone repositories. This means that submodules have their own branches and history.