Update git submodule to latest commit mod#
Update git submodule to latest commit update#

Update git submodule to latest commit update#

a script to update the parent repository's commit pointers. Not very practical, since you would have to hardcode n paths to all n submodules in e.g. This would be done by git submodule foreach git pull origin BRANCH New stuff has happened in one or more submodules, and I want to 1) pull these changes and 2) update the parent repository to point to the HEAD (latest) commit of this/these submodules.

Scenario 2, which I think is what OP is aiming at This is, as pointed out, done with git submodule foreach git pull origin BRANCH Using my parent repository's pointers to submodules, I want to check out the commit in each submodule that the parent repository is pointing to, possibly after first iterating through all submodules and updating/pulling these from remote. It seems like two different scenarios are being mixed together in this discussion: Now push your new version of the main project: git push origin masterįrom this point on, if anyone else updates their main project, then git submodule update for them will update the submodule, assuming it's been initialized. Git commit -m 'Updating the submodule 'mod' to the latest version' Now go back to the main project, stage the submodule and commit that: cd.

Update git submodule to latest commit mod#

So, in your case, you should find the right commit in the submodule - let's assume that's the tip of master: cd mod You also need to explicitly add the new version of the submodule in the main project. The submodule is really an independent repository - just creating a new commit in the submodule and pushing that isn't enough. git submodule update tries to check out that commit in each submodule that has been initialized. Your main project points to a particular commit that the submodule should be at. If so, do a reset in your local submodule directory and in your project parent directory, run again: git submodule update -init -recursive It can happen due to a file deletion in your submodule, etc. Most of the time the local change might not be the one you want to commit. Sometimes this still doesn't work, because somehow you have local changes in the local submodule directory while the submodule is being updated. Or if you have recursive submodules run: git submodule update -init -recursive In your project parent directory, run: git submodule update -init

This is equivalent to running git pull in each submodule, which is generally exactly what you want. Instead of using the superproject’s recorded SHA-1 to update the submodule, use the status of the submodule’s remote-tracking branch. This option is only valid for the update command. Will fetch the latest changes from upstream in each submodule, merge them in, and check out the latest revision of the submodule. Running git submodule update -remote -merge Git 1.8.2 features a new option, -remote, that will enable exactly this behavior. Or, if you're a busy person: git submodule foreach git pull origin master Git commit -am 'Pulled down update to submodule_dir' # Now the submodules are in the state you want, so # Time passes, submodule upstream is updated Git submodule add ssh://bla submodule_dir So in summary: # Get the submodule initially

If you want to update your submodules to the latest commit available from their remote, you will need to do this directly in the submodules. The git submodule update command actually tells Git that you want your submodules to each check out the commit already specified in the index of the superproject.