I think everyone would agree that the above commit history is bad, and should be avoided. But solving that issue by adopting a squash-on-merge policy is like d

I think everyone would agree that the above commit history is bad, and should be avoided. But solving that issue by adopting a squash-on-merge policy is like doing surgery with a chainsaw. There are better tools for the job.