|
|
|
|
|
|
by SamBam
1942 days ago
|
|
|
Exactly. It's also great to compartmentalize different aspects of your change. Often my changes are 1. Refactor the existing code to support the new feature 2. Add the new feature It's great to keep these separate, because someone can look at number 1 and see that the two versions of the code ought to be functionally the same (same tests pass, app looks the same, refactor is easy-to-understand), and look at number 2 and see the new feature. There are countless other times where you want to tell the "story" in a logical fashion. (Honestly, I expect that there is a significant correlation between being a good git committed and being a clear story-teller.) |
|
|