When we edit the URLs in .gitmodules and run git submodule update --init --recursive, it does not use the new URLs but the original ones. Because public user don't have access to the original URLs, they got errors.
What did you expect to happen?
When we run git submodule update.., it should use the new URLs that we specified in .gitmodules.
Possible solution:
git submodule update.. use .git/config file and not .gitmodules. So the changes we made in .gitmodules need to be reflected in .git/config before we run update command.
We can achieve it by running git submodule sync.
git submodule update.. relies on .git/config file and not .gitmodules. So we need to sync the changes from .gitmodules to .git/config before we run update command.
We can do that by running git submodule sync.
If this finding is correct then updating the README.md file would be helpful for other users who encounter the same issue.
General Information
This issue is applicable to public users only.
What happened?
When we edit the URLs in
.gitmodulesand rungit submodule update --init --recursive, it does not use the new URLs but the original ones. Because public user don't have access to the original URLs, they got errors.What did you expect to happen?
When we run
git submodule update.., it should use the new URLs that we specified in.gitmodules.Possible solution:
git submodule update..use.git/configfile and not.gitmodules. So the changes we made in.gitmodulesneed to be reflected in.git/configbefore we runupdatecommand.We can achieve it by running
git submodule sync.git submodule update..relies on.git/configfile and not.gitmodules. So we need to sync the changes from.gitmodulesto.git/configbefore we run update command.We can do that by running
git submodule sync.If this finding is correct then updating the
README.mdfile would be helpful for other users who encounter the same issue.