It sounds like what you want to do can be achieved from git v2.13 on with the new –recurse-submodules option of git checkout. From the git-checkout manual page: –[no-]recurse-submodules Using –recurse-submodules will update the content of all initialized submodules according to the commit recorded in the superproject. If local modifications in a submodule would be … Read more
To have one git repo “inside” another, look at git submodules: http://git-scm.com/book/en/Git-Tools-Submodules By making pychargify a submodule of your django project, specific revisions of your django project can be associated with specific revisions of your pychargify project. That can be really useful. I’m not sure exactly what the dangers are of the approach you describe, … Read more
Using git-hg. First, make sure there is a (non-Mercurial) git submodule under your main repository. If you don’t have other submodules yet, just create a dummy submodule for some library other than core-plot, for instance: main-repo $ git submodule add https://repo.url.com/repo.git repo Second, clone the core-plot library into some directory. main-repo $ git-hg clone https://code.google.com/p/core-plot/ … Read more
These two files contains absolute submodule path: {submodule}/.git .git/modules/{submodule}/config So, if you moved the repo, the absolute path in these two files are not valid, and cause the ‘not a git repository’ error. Just fix these files manually. Update: 1.) Delete the relevant section from the .gitmodules file. You can use below command: git config … Read more
Running this in the main repository should do the trick: git pull –recurse-submodules According to the other discussion, especially as @Tobu pointed out in his comment over there, if the error persists, it might be needed to first: remove both the submodule worktree (ext/blah) and the matching folder inside the GIT_DIR (.git/modules/ext/blah) Alternatively, you could … Read more
The issue is that git can’t find the public key needed to download the repo from your server, the solution is to use the public url. In the file .gitmodule you will find the following entry: [submodule “example”] path = example url = git@github.com:webhat/example.git The URL need to be changed to the public URL for … Read more
You should add .gitignore within each of your submodules. Since said submodules are like nested Git repo, they take care of their own ignore rules, and their status wouldn’t be influenced by the .gitignore of the parent repo (as explained here). For a vim-specific setting, as Randy Morris mentions in the comment, see the SO … Read more
What I did was to run: git rm -rf –cached myuntrackedfolder This tells git to forget about it (since it was being tracked formally). Then I used: git add myuntrackedfolder to add it and I was good to go.
I ended up doing this: Create a submodules directory. Add the submodule in this directory. Create a symlink to the specific directory inside the submodule. This way you have default Git submodule behaviour and in your project you only use a subset of the whole submodule.
After cloning the repository containing your submodules, the following command will checkout the master branch on all of these in one go: git submodule foreach –recursive git checkout master