When the developer creates a commit with the submodule at a particular version, that’s a strong statement that the supermodule works with the submodule at that exact version. If his code does actually work with the company’s version of the submodule, I think the right thing to do is for the developer to: branch the … Read more
I had the same error: radato$ git submodule update fatal: git upload-pack: not our ref somehash0 fatal: remote error: upload-pack: not our ref somehash0 fatal: Fetched in submodule path ‘dashboard’, but it did not contain somehash0. Direct fetching of that commit failed. So I deinitialized the submodule: radato$ git submodule deinit -f dashboard Cleared directory … Read more
This can (thankfully) be easily solved by modifying the .gitmodules file on-the-fly on Travis, so that the SSH URL is replaced with the public URL, before initializing submodules. To accomplish this, add the following to .travis.yml: # Handle git submodules yourself git: submodules: false # Use sed to replace the SSH URL with the public … Read more
You can do what you want, but your one, two, and three would need to be accessible to whoever will need to clone them—this is not usually the case for “random” development repositories. If you do set this up, you will need to be very careful not to delete “your” repository (or make it otherwise inaccessible) … Read more
Go into the directory where the submodule resides and git checkout the correct branch/commit. Then go up one level and git add and git commit the directory. This will check in the submodule with the correct commit. And don’t forget to run git submodule update –recursive on the other clients after updating them.
You need to do git submodule update –init –recursive. The problem here is the submodule C is never being initialized in the first place.
You forked the Drupal repo? Does it already have sub modules added in .gitmodules? If so you only needed to clone their branch and perform git submodule init git submodule update You don’t need to re-add their own sub modules to the repo. Now if you want to add additional submodules you have to perform … Read more
UPDATE There are two general reasons why Git will ignore a file: gitignore and submodules. To be more specific, the following conditions will cause Git to ignore a file when ‘git add‘ is invoked: The file matches a pattern $GIT_DIR/exclude. The file matches a pattern in a .gitignore file inside the repo. The file matches … Read more
You just discovered the lack of overridden dependencies with Git submodules: If Super depends on Core, its dependency of Core should “override” the ones A and B have with Core. The only way to emulate that would be to create your Super project the way you did, and to remove the sub-module Core of A … Read more
The way that the status of git submodules is reported has changed a lot over recent versions of git, so you should really include the output of git –version as well for us to be able to help accurately. However, in any case, the output of git diff example.com/soundmanager should tell you more. If you … Read more