As I go a-yak-shaving, I find I need to commit changes in reverse order of making them: Feature A needs bugfix B that necessitates change C that needs infrastructure D… When done with Z while A to Y are incomplete, I must isolate Z from all the half-baked changes and commit it.
So the cow-orkers at $BigCo demanded that I split my commits in smaller ones — but in the end, even after removing lots of small independent changes found along the way, the meat was still one big commit, because that's what happen when you refactor.
-
-
good way of putting it: the core of a refactoring probably needs to be put into a single—possibly large—commit.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!