Capistrano can deploy branches, tags, and sha's.
In order to support tags and sha's it needs to ensure there is no ambiguity
that's left on the remote box when it's done.
'deploy' was chosen so that you KNOW that the sha it's pointing to is something
other than a real branch name.
For examp
"deploy" branch name is hardcoded in
lib/capistrano/recipes/deploy/scm/git.rb at line 146 then you shouldn't
change it (actually you can by overriding this method).
Why you need it?
2013/2/26 fré de vries
> Hi all,
>
> When i run 'cap deploy' , capistrano checks out a new branch in the just
Hi all,
When i run 'cap deploy' , capistrano checks out a new branch in the just
created releases/x/ directory.
As i can see on my screen during deployment, Capistrano does this with the
command
*git checkout -q -b deploy a4f187cf3dbd4294dc2fb4cc31b222eed79c51d5*
*
*
as you can see,
