Guys and people at large, I've updated the Git SCM module, and it works for me... Could some others please have a look and critique?
http://github.com/adamsalter/capistrano/commit/2283dea45a6ff15e85851136860f366c76257022 It still works for all the test cases I can think of (and almost seems faster ;) To see for yourself checkout my repo... I use the following command to make changes to the gem and install: rake repackage && sudo gem install -l --no-ri --no-rdoc pkg/ capistrano-2.3.0.gem Thanks, -Adam On May 5, 11:47 pm, "Mislav Marohnić" <[EMAIL PROTECTED]> wrote: > On Mon, May 5, 2008 at 2:34 AM, Adam Salter <[EMAIL PROTECTED]> wrote: > > I've actually investigated this myself... > > I don't think: > > set :remote, "staging" > > does what we think it does (neither did '-o staging' for that matter), it > > basically just renames the remote reference on the deploy server from > > 'origin' to whatever you choose. > > Well, yes. I thought that you wanted to do this (since you used the -o > option). I corrected you to move it out of the repository URL because there > was already an option for it in Capistrano. > > I was wrong to say that the :branch option is never used. It actually is in > "recipes/deploy.rb". It uses the branch name (or "HEAD") to get the commit > ID *from your local repository*, then uses that ID to do a remote checkout > (no matter what strategy you use). > > In conclusion, if you want to deploy from the "deploy" branch, you have to > have that branch set up locally and all its commits pushed to your remote > repository as well. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
