That error means that projectfolder is already staged (already exists in the index). To find out what’s going on here, try to list everything in the index under that folder with: git ls-files –stage projectfolder. The first column of that output will tell you what type of object is in the index .
Issue with adding common code as git submodule: already exists in the index Translate. I’m new to git and would appreciate help with adding submodules . I’ve received two projects sharing some common code. The shared code was just copied into the two projects. I created a separate git repo for the common code and removed it from the projects …
If there is an entry registered in the index , you will need to remove it before being able to add your subrepos as a submodule . (as explained in Issue with adding common code as git submodule: “already exists in the index ”) All this assumes that you are at the root folder of a currently cloned repo, which will act as the parent repo of …
is the relative location for the cloned submodule to exist in the superproject. If does not exist , then the submodule is created by cloning from the named URL. If does exist and is already a valid Git repository, then this is added to the changeset without cloning.
11/28/2020 · Module Already Exists in Index . in file .gitmodules – delete links to submodule (whole section with submodule name) in file . git config – delete links to submodule , as in previous step. in folder . git modules – delete folder with relative path similar to relative path of problem module. References, Git – Submodules, Git – Submodules, Issue with adding common code as git submodule : already …
How to `git submodule add` Existing sub Repository …
By default, the git pull command recursively fetches submodules changes, as we can see in the output of the first command above. However, it does not update the submodules. This is shown by the output of the git status command, which shows the submodule is …
