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. Which doesn't change any functionality at all as far as I can see. The remote reference may as well be called 'origin'. (ie then remote branches become origin/ staging, origin/better_branch etc.)
The problem is partly that git is a full DVCS. The github version of the repo, and the local, and the deploy server could all have totally different repos. I think the assumption should be that the github version and the deploy server ones are the same. The local one could differ. -Adam On 04/05/2008, at 10:25 PM, Mislav Marohnić wrote: > Hey Adam, > > On Sat, May 3, 2008 at 4:23 PM, Adam Salter > <[EMAIL PROTECTED]> wrote: > > set :repository, "[EMAIL PROTECTED]:adamsalter/app_name.git -o staging" > > First of all, this line is wrong. It should go like this: > > set :repository, "[EMAIL PROTECTED]:adamsalter/app_name.git" > set :remote, "staging" > > But after that, it still won't work. This is because the ":branch" > options is not used for anything. It always defaults to master. > > The option *is* used inside a method named "head", but that method > is never called. This is a Capistrano bug for sure. > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
