Moving to the dependencies-override section did not make it any better.
Then, another developer who wants to have submoduledirectory changed to that tag, does this. git add submoduledirectory git commit -m 'moved submodule to v1.0' git push. A superproject is a Git repository in which the superproject Git goes into a submodule Git and does a git checkout hash (or git switch -detach hash), by hash ID, to get a detached HEAD in the submodule Git repository. It’s like there is some weird file sync issue going on. If you want to move the submodule to a particular tag: cd submoduledirectory git checkout v1.0 cd. A submodule is a Git repository (so it has its own branch names, tag names, and commit objects).
And to my surprise, the second group of commands succeeds? It was all very confusing. git/submodule_path/config file is updated successfully and git submodule sync succeeds?!Īnd the first command fails (as we have observed), but I || : so that the build continues. However after the CI has failed, and I’m sshed for my 30 minutes, I can type in git submodule sync and the. git/submodule_path/config files remains unchanged. gitconfig, The ubuntu user definitely appears to have write permissions (664), and yet the. I have sshed into the CI session, and typed git submodule sync several times, and ls and cat. I’ve actually investigated this problem (before finding this post). Or at least: can you add a way to clear my cache myself? gitmodules urls so if it’s not something you can fix maybe I can do something differently. So 1: is this a bug that you guys should/can fix? Or 2: what can I do to avoid this in the future? I will definitely be continuing to change. I had to wait almost 2 weeks to get my cache cleared so builds would start passing again (I’ve had to disable my check for a passing build in my deploy script this whole time). I even tried to change it in ssh and rebuild hoping it would cache the result of the ssh run, but no dice. I rebuild with ssh, log in, and check the remote for that submodule, and it’s still pointing to that old url, despite that url not existing anywhere in my codebase. By the time it goes to check out my submodules it always complains that the commit I’m looking for is not found in the repo.
Git submodule get update#
I have tried adding git submodule sync & git submodule update -init -recursive to my post-checkout commands, I have tried deleting the submodule entirely from my repo, committing that, and then re-adding next commit. Manaswini explains how Git submodules and subtrees can help you with in-house dependency management.
Git submodule get software#
It will always point to the old url no matter what I try to do to fix it. In this course, software engineer Manaswini Das helps you discover and learn to use Git subtrees and submodules, the tools that enable you to manage multiple repositories from a single repository. At whichever point it gets received I will switch back to the source repo.ĭuring this time, the cache of. I will make the change and submit a pull request upstream but if/until it gets approved I need to use my fork to use this feature. I will be using a submodule, decide I need a new feature, fork it and update my repo to point to my fork. I’m running into an issue with the cache. I was directed here by the customer support widget.
0 kommentar(er)
