3 ms·
The key principle is that the software should always correctly work at any point in the chain of commits, so you must squash commits that are "oops, fix X in pr
by devit 11y ago
The key principle is that the software should always correctly work at any point in the chain of commits, so you must squash commits that are "oops, fix X in previous commit".
Once that is satisfied, commits should be as small as possible, so that information about the grouping of changes is preserved.
- chmaynard 11y agoThis advice seems very sensible. Thanks for adding some valuable ideas to the discussion. I'm now reading the git documentation on re-writing history: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History