I have a project pointing to one remote git repository on github. I changed it to point to another remote repository on github. It initially refused to deploy because the public keys were set up with other repository. So I generated new keys for the new repository and it deployed fine. What astonishes me is when I logged into the server and checked the git remote branches on it:
$ git remote -v origin [email protected]: guarddog/guarddog.git (fetch) origin [email protected]: guarddog/guarddog.git (push) The remote pointer to the old repository was completed removed and now it pointed to the new repository. When and how did capistrano do all this during "cap deploy"? When I did the changes locally, it was something like this: git remote -v origin https://github.com/usera/usera.git (fetch) origin https://github.com/usera/usera.git (push) git remote add guarddog https://github.com/guarddog/guarddog.git git remote -v guarddog https://github.com/guarddog/guarddog.git (fetch) guarddog https://github.com/guarddog/guarddog.git (push) origin https://github.com/usera/usera.git (fetch) origin https://github.com/usera/usera.git (push) git checkout -b master guarddog/master I don't see anything like that in the cap deploy process. -- -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en --- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
