Comments on: Changing git submodule URLs

By: david

david — Fri, 12 Jun 2009 14:05:25 +0000

seems there is a way to do that properly:

in the submodule directory do:
git remote update
git merge origin/master

then you can add, commit and push the change to the submodule in your main project.

By: Matthieu Sadouni

Matthieu Sadouni — Sun, 25 Jan 2009 10:25:33 +0000

Thanks for the tip. Just another thing that caused me trouble : when deploying with Capistrano you need to clear the shared/cached-copy directory or it will try to clone the old version of the plugin and fail with “Unable to checkout ”.

I now use this task when i change a submodule :

namespace :deploy do
task :clear_cached_copy do
run <<-CMD
rm -rf #{shared_path}/cached-copy
CMD
end
end

and deploy with :
cap deploy:clear_cached_copy
cap deploy

Maybe you could clear only the plugin subdirectory instead of the whole cached-copy and pass the plugin name to the task, I’ll have to try that.

By: Tom

Tom — Tue, 01 Jul 2008 14:34:00 +0000

Out of interest, what’s Wrong with The Wrong Way? As long as you fix up the repository URL in your local clone of the submodule (e.g. edit its .git/config, or just blow it away and git submodule update from scratch) it seems like it should chug along fine without having to completely nuke and re-add the whole submodule. What gives?

By: Steve Eley

Steve Eley — Mon, 09 Jun 2008 19:59:49 +0000

Yes, thank you! We’ve been trying to make submodules work for a repository of code shared between several applications, and the things submodules don’t do that svn:externals did (like auto-updating) have been driving us nuts. We’re starting to wonder if it’s more trouble than it’s worth.

By: ch0wda

ch0wda — Thu, 05 Jun 2008 21:30:57 +0000

Adam,

Thanks, I have learned from your mistakes. This yak still has all it’s hair.