Hopefully I haven't misunderstood. : Create a new repo on github, follow it's instructions for adding an existing project. (something like 'git remote add origin [email protected]/blablabla' )
Now, just push and pull from your github repo instead. When you want to send changes to heroku, do a push to heroku. Use different branches for different release stages (staging, production etc). Does that make sense? On Dec 1, 1:59 pm, Graeme Simpson <[email protected]> wrote: > Hi there, > > I have an app on heroku at the moment and so far we've just been using git > on heroku as our main repository. > > We need to switch things around so we use github most of the time and have a > separate app for staging and testing. > > I found this excellent guide for setting up github with > herokuhttp://suitmymind.com/blog/2009/06/02/deploying-multiple-environments... > but it only covers new applications. > > Does anyone have any instructions (or could point me at an alternative > guide) for switch the repos around to use github as the master? > > Thanks, > Graeme -- 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.
