Assuming PRs and associated feature branches are substantial[0], I'm a proponent of merging w/o squashing commits. When running `git bisect` or simply doing archaeology on a code base where the previous author(s) left the organization, I've never regretted reading granular commits--only too coarse.

[0] Largely depends on the team's workflow and the functional size of feature branches. If there are a lot of smaller commits made to develop/main/etc., then you can probably get away with squashing.