Update Submodules with Git
Git submodules seem to confuse people and I can probably count myself in that group of people that are confused. Their code is kind of part of the codebase, kind of isn't. Pulling the latest code from the overall project doesn't pull the updated submodule code, so sometimes you get errors and don't know what's going on. To ensure your submodules are always up to date, run this via the command line:
git submodule update --init --recursive
This command ensure your existing submodules are current as well as adds new submodule code whenever appropriate. I like to run this at least once a day just to make sure my code is always up to date. You never know what some of your collaborators have contributed (if you work in a team setting), so running this daily is useful!
It's no secret that Facebook has become a major traffic driver for all types of websites. Nowadays even large corporations steer consumers toward their Facebook pages instead of the corporate websites directly. And of course there are Facebook "Like" and "Recommend" widgets on every website. One...
CSS animations aren't just for basic fades or sliding elements anymore -- CSS animations are capable of much more. I've showed you how you can create an exploding logo (applied with JavaScript, but all animation is CSS), an animated Photo Stack, a sweet...
Zohaib Sibt-e-Hassan recently released a great mouse gestures library for MooTools called Moousture. Moousture allows you to trigger functionality by moving your mouse in specified custom patterns. Too illustrate Moousture's value, I've created an image download builder using Mooustures and PHP.
The XHTML
We provide...
I've always seen Digg as a very progressive website. Digg uses experimental, ajaxified methods for comments and mission-critical functions. One nice touch Digg has added to their website is their hover share widget. Here's how to implement that functionality on your site...
While this is definitely a useful command, it’s worth noting that updating your submodules basically just checks out the revision as defined in the repository. If you’re maintaining a project that uses submodules, this won’t get the latest code for that submodule, so much as it just ensures that the submodule is on the commit as defined.
For example, I maintain all of my dotfiles in a Git repository, which includes several submodules (Vim plugins, mostly). This command doesn’t actually update the submodules to the latest revision on their branch. If I want to go into each submodule and pull the latest code for each (which can be horribly risky, caveat emptor), I can do something like this:
git submodule foreach ‘git checkout master && git pull origin master’
That will go through each of my submodules, ensuring that they are on the latest master branch. That may not be the desired or best behavior, but it is something I learned about with regards to `git submodule update`.
Hi!
I’m very interested in git’s submodules but I can’t find a tutorial that I can understand properly
Could you address this? (or at least point me to your reference tutorial)
Thanks a lot!
Why not create a Git hook for this?
You could use post-checkout & post-merge to automatically fire this on every branch checkout or pull, respectively.