I use squash merge and make sure each PR is small enough to justify being just one commit. Big things which are too big to fit in a single PR can be tracked in

I use squash merge and make sure each PR is small enough to justify being just one commit. Big things which are too big to fit in a single PR can be tracked in other ways, such as mentioning a Github issue number or project management issue ID in the commits. Individual commits on a PR/feature branch are useful to check what's changed since the last review (I silently despise developers who force-push their rebased commits when fixing things, making it basically impossible to re-review). I just wish it was easier to detect locally whether my development branch has been squash-merged so I could script the deletion of them.