Thanks - I guess I should have been more clear - I'd like to push but not have heroku pull in the branch and try to deploy it. Basically I need to keep master deployed, but be able to push other branches to the git repo heroku gives me. That make sense?
On Nov 30, 10:39 pm, Nick Quaranto <[email protected]> wrote: > git push heroku v2:master > > From the git docs: > > The special refspec : (or +: to allow non-fast-forward updates) directs git > to push "matching" branches: for every branch that exists on the local side, > the remote side is updated if a branch of the same name already exists on > the remote side. > > http://www.kernel.org/pub/software/scm/git/docs/git-push.html > > On Mon, Nov 30, 2009 at 10:38 PM, Kyle Bragger <[email protected]>wrote: > > > > > What happens if I am working in branch (called "v2" for instance) and want > > to do a 'git push heroku'? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<heroku%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
