Retrospectively add –recursive to a git repo
If I’ve forgotten to add this magical flag when cloning, as can happen, how do I now go and get any submodules?
- What is the cleverest use of source repository that you have ever seen?
- Keeping development databases in multiple environments in sync
- How to deal with committer name change in Mercurial
- How do I get files from my svn repo to staging or production system?
- git: how can I programmatically determine if I need a pull or push?
- Backup a local working directory on BitBucket - clone or push
Additionally, how can I set the recursive flag as a default for future clones?
4 Solutions collect form web for “Retrospectively add –recursive to a git repo”
You can do it with this after a simple top-level clone:
git submodule update --init --recursive
I would not recommend making clone do this by default. The proper way to do this if you are using submodules aggressively for development and not just linking to 3rd party OSS libs on github that you may upgrade once in a blue moon, is to use git slave or subtree.
Hope this helps.
From the root of your repo:
$ git submodule update --init --recursive
That will update any and all registered submodules, initializing them if need be to the value as found in the .gitmodules file, and also recurse into complex submodules (ones with submodules of their own) and initialize and update them as well.
The easiest way I know of to make cloning recursively the default would be to shadow
git clonewith an alias
$ git config --global alias.clone = 'clone --recursive'
As far as adding options always, I think that’s the idiomatic method.
git submodule init,
git submodule update
Unfortunately, I do not see an option to enable recursive by default, however.
It appears you can’t override “clone” with alias “clone”, so it’s a new alias (Abizern’s solution) or “–recursive”.
Is it possible to override git command by git alias?