4 ms·
The problem with rebasing is you might break every one of those commits, which defeats the purpose of chunking the work like that in the first place (since its
by bananaface 6y ago
The problem with rebasing is you might break every one of those commits, which defeats the purpose of chunking the work like that in the first place (since its no longer an honest reflection of what was happening/what worked at each point).
- nicoburns 6y agoI usually rebase and then squash so that becomes a non-issue. I often find I want to commit more often than the code is in a working state, so I like to be able to erase that history later. I try to keep the whole branch small enough that it'a fine being in one commit.