> The poor commit quality is your issue here, and squashing is merely a way to avoid addressing it. Just like I said: it's like driving reverse because you don

> The poor commit quality is your issue here, and squashing is merely a way to avoid addressing it. Just like I said: it's like driving reverse because you don't want to learn how to shift gears! > That only makes squashing a good tool to use to make a big mess a slightly smaller mess. You're right, in cases that the repository is so cluttered this may be a palliative solution to avoid things to get worse. Squash exists, so it is a tool that can be used if you know what you're doing. But it being useful for rescuing in some situations doesn't mean that can be used in all situations. It's like taking pills instead of vaccines. There are other tools in this category, such as git push -f: it is a useful tool that you may use when it's necessary if know what you're doing. This doesn't mean that it should be used as first option. Same for squash