3 ms·
Use squash and merge instead. It's built right into GitHub, that way your history will look like: Implement feature A Implement feature B
by unfunco 8y ago
Use squash and merge instead. It's built right into GitHub, that way your history will look like:
Implement feature A
Implement feature B
- u801e 8y agoIn either case, you end up with commits that have large diffs and touch many parts of the code base. Most features require multiple commits to implement. As far as I know, Github does not provide a facility to squash into multiple commits.