This shouldn’t actually affect anyone in practical terms because one of the things github does really well is to redirecting old repo URLs, and the old one should just continue to work. But anyone cloning it should switch to using the new URL just to be future-proof!
Some git and bash helpers for future-proofers:
# If you don't have multiple remote urls, like when doing a straight clone: git remote set-url origin https://github.com/WeAreROLI/JUCE
# If you have multiple remote urls, like a fork of yours and JUCE as 'upstream': git remote set-url upstream https://github.com/WeAreROLI/JUCE
Being somewhat git-phobic, should I run that git command before changing the remote URL in Xcode or after? Or do I have to change anything at all in Xcode if a run that command?
No need to do anything in Xcode if you run either of the commands above. HTH!
Hi there, are these the commands I should use to update my references if I have Juce as a submodule in my repo (issued in the submodule folder)?
Not really, for the case of JUCE as submodule, I’d suggest to do it like this:
In the main repo (the one that has JUCE as submodule), edit the
.gitmodulesfile and update the URL for JUCE, for example like this:
[submodule "juce"] path = juce url=https://github.com/WeAreROLI/JUCE
While still in the main repo, issue the following command, which will automatically propagate your change to the repo of your JUCE submodule:
git submodule sync
For that, it’s easier to manually edit and commit the
It will exist in your repository, and look something like this initially:
[submodule "JUCE"] path = JUCE url = https://github.com/julianstorer/JUCE
After you edit the file, you’ll have to resync, and maybe update, your submodules:
git submodule sync git submodule update --init --recursive --remote
Okay, no clue why I didn’t see your post at first.
We’re git crunching machines
Literally dozens of us on the JUCE forums, dozens!
Thanks git crunchers !