3 ms·
Ideally your commits are squashed and then merged anyway, GitHub just still uses merge as a default since I assume it's the most "logical" to git newbies.
by meibo 4y ago
Ideally your commits are squashed and then merged anyway, GitHub just still uses merge as a default since I assume it's the most "logical" to git newbies.
- Avamander 4y agoOnly a polluted commit history should be squashed - bad commit messages, incorrect segmentation, fixes to earlier commits etc. Think of it this way, if the commit works on its own it should remain as-is. If it's a hodgepodge of ten commits that inter-depend then they probably should be squashed.