Greetings, We're using Heroku for our production environment and have recently created a production branch, with the hope that we can continue feature development on our master branch per most Git-based projects. However, Heroku seems to enforce that 'master' is the deployed branch. This can be circumvented by creating another branch called 'edge' or similar and pushing new changes there. Our issue now is that we want to create an additional Heroku deployment for our staging environment and push the 'edge' branch there. Since Heroku only responds to changes on 'master', how can we maintain the pristine, production-ready state of the master branch for our production environment while pushing bleeding-edge changes to the staging environment?
Is anyone else using Heroku for two environments running different branches of the same repository on each? What is your solution? Best regards, T.J. VanSlyke --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
