Hacker News Reader

One problem with this is that git gets used as a deployment tool as well as a version control system.

Trying to get something to run on Heroku involved making lots of small changes just to get things to run on the server the same as on my dev machine.

When you do that 10 or 20 times the commit message become somewhat meaningless.

View on HN

I also commit like 20 things to get Heroku working properly. But after I am done with that, I `rebase` it into one commit. Then I push it into my `origin/master`, and force push `heroku/master`.

generally when I'm trying this stuff I'll make a new branch to work off of and deploy from that. when I've figured out how it needs to work, I'll squash the commits and merge into master.

Reply on news.ycombinator.com