Good Git deployment using branches strategy with Heroku?

Question

What is a good deployment strategy to use with Git + Heroku (Ruby on Rails)?

Currently, the way I work with my origin Git repository: All features (or \'stories\') are f

Answer 1

In the Gemcutter project we simply have a production branch. Any changes that we want to see on the production site get merged into that branch, and then deployed with:

git push heroku production:master

The staging branch serves a similar purpose for the staging site (also on Heroku)