Pull Git Submodules After Cloning Project from Github
I Have a Project That Has Specified Submodules in It. Everything Works Well on the Dev Machine. I Have Commited. Gitmodules File and Pulled on the Production...
I have a project that has specified submodules in it. Everything works well on the dev machine. I have commited .gitmodules file and pulled on the production. However it does not pulled submodules.
If I go into submodule directories and call git pull, nothing happens.
What is the proper way to pull those submodules in the new project ?
4 Answers
From the root of the repo just run:
git submodule update --init
If you need to pull stuff for submodules into your submodule repositories use
git pull --recurse-submodules
But this will not checkout proper commits(the ones your master repository points to) in submodules
To checkout proper commits in your submodules you should update them after pulling using
git submodule update --recursive
If there are nested submodules, you will need to use:
git submodule update --init --recursive
I just want to share these.
First way,
git submodule init && git submodule update
The below is just basically combining the first way,
git submodule update --init
If there are any nested submodules, Iglesk's answer is the way to go.
Sarah Jenkins is a veteran tech journalist with over 12 years of experience covering artificial intelligence, mobile innovations, and digital ethics. Her insights have appeared in leading technology publications worldwide.
