On the other side, the command git submodule foreach:Įvaluates an arbitrary shell command in each checked out submodule.īecause of that and assuming that the OP knows what the git pull command does, it's easily deducible that the combination of them can actually update all the submodules to the latest available commit. Update the checkout to latest from svn: git submodule foreach git svn rebase, or git submodule foreach git. That means that it doesn't update the submodules to the latest available version, instead it checkouts the actual commit with which the superproject expects to work. Update the registered submodules to match what the superproject expects by cloning missing submodules and updating the working tree of the submodules. The git submodule update command does the following: It wont be tracked from the parent repo: said parent repo only references the gitlink (special entry in the index) representing the SHA1 of the submodule repo. I dont want to track it or push to server.
I'd rather give a look at the documentation to fully understand the differences between the above mentioned commands, but I'll have also a try explaining them below. Then, a git status from its parent repo should mention the (submodule) folder anymore. IfSubmodules are very static and only track specific commits. 2) Remove the submodule repository from the superprojects. A git submodule is a record within a host git repository that points to a specific commit in another external repository. So this: git fetch -all -tags git reset -hard tags/v2.11.0 is a little weird, 1 but not entirely crazy. Your main repository will, after cloning or running git fetch if appropriate in your clone of the other Git repository, run git checkout hash using this raw hash ID. The raw hash ID of some commit that should be in that other Git repository. The tags/v2.11.0 tag in the superproject is therefore a name forthat is, represents the number, or hash ID ofa particular commit in the superproject. This will reset the repo even if you have valuable uncommitted changes, so use with care resetgitrepo(skipclean: true) If you want git clean to be. That lets your Git run git clone if needed, during git submodule update -init for instance.
git/config: git submodule deinit -f path/to/submodule. 2 Answers Sorted by: 1 A tag is a name for a commit. To get them along with the main project you can either use the -recursive parameter to the git clone command or use the command git submodule update -init once you have cloned the repo that contains them. The first three steps of the following are how you permanently delete a submodule the fourth step will tell git to restore the module, but not to reinitialize it. You can simply use git submodule foreach git pull to keep them updated once downloaded.
0 kommentar(er)
