4 ms·
That's a better solution than changing the Git(Hub) model. If this works for you, then why the need to change anything?
by mmcnl 3y ago
That's a better solution than changing the Git(Hub) model. If this works for you, then why the need to change anything?
- jen20 3y agoBecause squash merging results in horrifically poor commit messages that are use to no one in future, because GitHub can’t be bothered to implement anything beyond a simple textarea for editing them.
- u801e 3y agoNot only that, they also result in commits that change a lot of files and make many changes in each file. Try to revert one of those commits is difficult after other changes have been merged into the main branch.