Geek Answers Handbook

Automatically git commit between steps Red, Green and Refactor?

I'm always interested in trying new things with my workflow, and I thought it might be an interesting experiment to automatically commit between red, green, and refactoring steps, but then manually crush the commit after the completion of a certain function (and before pressing) .

I'm just wondering if anyone else has tried this before. I thought I read about it once, but I can not find any links.

I hope that one advantage may be to focus more on fixation as well as on visualizing my workflow so that I can improve it. For example, before the distribution, I see if the time between red and green is too long, or the number of code changes that I do is more than necessary between each step.

I was going to implement this as a guard plugin so that when saving the specification file or library, it launches the specifications and commits the change using a type commit message:

Green: 1621 examples, 0 failures, 2 pending (1659 tests/s, 0.0006 p/test)

The idea was that I could visually check this when crushing and determine where to group the corresponding Red / Green / Refactor, due to logical changes.

, , , .

+5
4

.

/ .:)

, "" Red/Green.

:

  • --amend 'Red', , , spec, ?
  • "", - lib?
+1

, , , . , () , . git , .. .. , / , .

+1

!! , ( ), Unit Testing, git, .

, . , , RED, , GREEN , RED , RED-.

...

, , , .

+1

I like it, and I thought it myself. I am not sure that I fully see its value. At first it turned red, I thought it would make it easy to return to my last known green state. After viewing JUnitMax, it has a built-in “return to green” function, so I didn’t feel like it, because I automatically made a transaction.

+1
source

More articles:


All Articles