Comments on: red, green, refactor … commit

By: Matt Wynne

Matt Wynne — Sun, 09 Nov 2008 14:47:00 +0000

High five. I do exactly the same now I work with git.

The nice think about commiting on red is that you can git pull –rebase on that code (if you dare) and make sure the work you do to get to green includes working with any of your team’s changes.

I like the git commit –ammend trick too, and will be using that – thanks Dan.

By: Kevin Rutherford

Kevin Rutherford — Thu, 30 Oct 2008 16:06:39 +0000

@Dan: Nice idea — I’ll try it

By: Dan Kubb

Dan Kubb — Mon, 27 Oct 2008 17:43:07 +0000

I follow a similar pattern to yours, except after green I use git commit –amend. This appends to the last commit rather than creating a new one. The reason I do this is that I prefer code in my remote repository to always be in a passing state. In the case of merging, rollback or rebasing (which I do often when I sync my local repo to a remote one that others are working on), it’s nicer not to have to deal with any red commits — once I rebase, fix any conflicts and make sure all the tests pass I know it’s safe to push.