Short answer: cd ProjectFooBarCommoneSubmodule git checkout master <Do your editing> git commit –all -m “Lots of fixes” git push submodule_origin master cd .. git add ProjectFooBarCommoneSubmodule git commit -m “Bumped up the revision of ProjectFooBarCommoneSubmodule” git push origin master The longer one: Git submodules are a dependency mechanism, where the main project (say A) defines … Read more
Git still think mysubmodule is a submodule, because it is recorded in the index with a special mode “160000”. See “git submodule update needed only initially?” for more. To check that, as in in this answer, you can do a: $ git ls-tree HEAD mysubmodule 160000 commit c0f065504bb0e8cfa2b107e975bb9dc5a34b0398 mysubmodule That doesn’t depend on the presence … Read more
Considering that the unit of work for git is a repository (or more precisely a repository content), I don’t think you can easily integrate one file. If you don’t need its history, you could consider simply copy it in your repo. But if you do need the history, then some git filter-branch (as in “git: … Read more
You can do it with this after a simple top-level clone: git submodule update –init –recursive I would not recommend making clone do this by default. The proper way to do this if you are using submodules aggressively for development and not just linking to 3rd party OSS libs on github that you may upgrade … Read more
As I mention in “git submodule tracking latest”, you can since git 1.8.2 (March 2013) make a submodule track the HEAD of branch: git submodule add -b <branch> <repository> [<path>] A submodule SHA1 is still recorded in the parent repo as a gitlink (special entry in the index) But a git submodule update –remote will … Read more
As the other answers explain, you can use two commands: git submodule status, or git ls-tree HEAD, taking only the lines where the second column is commit (if you have awk you can use git ls-tree HEAD | awk ‘$2 == “commit”‘). However, these commands give different results! What’s the difference? git submodule status always … Read more
Just run: $ git submodule update This will revert the submodule the to old commit (specified in parent-repo), without updating the parent-repo with the latest version of the submodule.
It seems that now (in 2019) installing latest GIT client could solve the problem according to comments below. This should be the best solution for now. I have the same problem as you. This is a bug in git: http://git.661346.n2.nabble.com/BUG-git-submodule-update-is-not-fail-safe-td7574168.html In short, for your problem, try: # rm -rf external_libraries/BEACHhtml # git submodule update It … Read more
git checkout –recurse-submodules was added to git 2.13 This is mentioned on the release notes at: https://github.com/git/git/commit/e1104a5ee539408b81566066aaa6963cb87d5cd6#diff-c24776ff22455a30fbb78e378b7df0b0R139 submodule.recurse option was added to git 2.14 Set as: git config –global submodule.recurse true man git-config says: Specifies if commands recurse into submodules by default. This applies to all commands that have a –recurse-submodules option. Defaults to false. … Read more
Note that the Jenkins Git plugin 2.0 will have “advance submodule behaviors”, which should ensure proper updates of the submodules: As commented by vikramvi: Advanced sub-modules behavior > “Path of the reference repo to use during submodule update” against this field , add submodule git url. Owen B mentions in the comments: For the authentication … Read more