I was directed here by the customer support widget.
I’m running into an issue with the cache. I sometimes change my remote urls in .gitmodules. I will be using a submodule, decide I need a new feature, fork it and update my repo to point to my fork. 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. At whichever point it gets received I will switch back to the source repo.
During this time, the cache of .git seems to cause problems. It will always point to the old url no matter what I try to do to fix it. 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. 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. 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.
I even tried to change it in ssh and rebuild hoping it would cache the result of the ssh run, but no dice.
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).
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 .gitmodules urls so if it’s not something you can fix maybe I can do something differently. Or at least: can you add a way to clear my cache myself?