I actually ended up solving this problem by maintaining two local repositories (pushing and pulling locally while developing). It's not ideal, but it's a simple local workaround that works, whereas I am assuming that the heroku guys would have to do some serious infrastructure magic in order to make what you are suggesting.
On Fri, Apr 24, 2009 at 10:51 AM, Damien MATHIEU <[email protected]> wrote: > > Hello, > > When I work on a new feature for my application, I do it in a specific > branch; I commit in that branch. > And when this feature is ready, I merge that branch to the master. > > I'd appreciate to be able to start the application on an other branch, > but with an other url. > > For example, have xxx.heroku.com on the branch master of the > application xxx. > And yyy.xxx.heroku.com on the branch yyy of the same application. > > The example above is only a suggestion and you might already have had > a different idea. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
