How to Use the Git Submodule Update Command by Example

The parent Git repository isn't always in sync with the latest git submodule. That's why you need to occasional do a git submodule update.
The git submodule update command can be a bit confusing though. It doesn't work exactly as one might think. If you don't add the --remote switch, it's not going to update your working directory like you might expect. In this Git remote update example we demonstrate how to update your git submodule the right way.

[@heathledger7291]

Short ,clear and to the point . This is a great video

[@cameronmcnz]

Thanks! I try to keep them simple. Nobody want to hear my views on world politics.

[@wabdih]

thanks. I was missing one tiny detail and this video cleared it up

[@cameronmcnz]

Glad I could help! Hopefully you got your answer quickly.

[@roberthevesi]

cool explanation, thanks!

[@cameronmcnz]

Glad I could help! Git submodules are fairly complicated, but once you've got it, you've got it!

[@_marlon]

Thanks for clarifying that!

[@douglascavalcante1811]

Thanks, it was much helpful!

[@ukemewilson4576]

Thank you

[@cameronmcnz]

Any time!

[@intoeleven]

why my git submodule update --remote failed?
* branch HEAD -> FETCH_HEAD
fatal: Needed a single revision
Unable to find current origin/HEAD revision in submodule path 'xxx'

[@angweteryila1532]

by mare looks you got that module wizard in your blood stream possess me bro