In the past few days I’ve attempted to update the “staging” copy of Digital.Grinnell at and learned a valuable lesson regarding workflow around Git and submodules. Specifically, I found the following resource to be most helpful:

In case that post ever disappers, here’s the gist of it…

The git submodule update command actually tells git that you simply want your submodules to each check out the commit already mentioned in the index of the superproject.

If you want to update your submodules to the most recent commit available from their remote, you’ll try this directly within the submodules.

So in summary:

# Get the submodule initially
git submodule add ssh://bla submodule_dir
git submodule init
# Time passes, submodule upstream is updated
# and you now want to update
# Change to the submodule directory
cd submodule_dir
# Checkout desired branch
git checkout master
# Update
git pull
# Get back to your project root
# now the submodules are in the state you wanted, so
git commit -am "Pulled down update to submodule_dir"

Or, if you’re a busy person:

git submodule foreach git pull origin master

And that’s a… break. When I return I hope to add some DG specifics.