2 ms·
> you instead spend doing very careful munging later and crafting very careful commits with git add -p and rebase I mean, I already do this, because I like to
by derefr 7y ago
> you instead spend doing very careful munging later and crafting very careful commits with git add -p and rebase
I mean, I already do this, because I like to be able to understand my commits as standalone historical artifacts. IMHO commits exist to be read (by your future self trying to figure out WTF you were on about most of all!) as much as they exist to change the state of the codebase.
Given that I'm already doing this, it wouldn't be any more work to use a workflow like this, I guess? (I still use branches. And have multiple git worktrees checked out at once from the same repo.)