Folks who squash their #git merges, I’m curious why you are making that trade-off. I’m guessing the pro argument is a cleaner merge graph?

The big argument against it for me is that you lose granularity for git bisect. I've often been able to narrow down breakage (sometimes long past the merge) due to individual commits in the merge. If I'd merged in a giant blob all I'd have had to go by is that giant blob. (1/2)

As to the “pro” argument: tooling (like for instance the excellent @fork_dev, see the screenshot) can allow you to fold your merges so they look squashed. I feel like that's the perfect combination - overview on demand without loss of granularity. (2/2)
@finestructure thank you for reminding about this feature. We'll try to improve it in the next update :).
@finestructure We just released Fork 2.43. You can check for updates.
@fork_dev Oh nice, it’s the branch detail on hover that's new, isn't it?