When squash merging, all commit messages are added to the extended description in the editor, which makes it far easier to remove useless comments and add in any necessary info as needed. All of that context can then be viewed via git show and other commands, while keeping the base branch's history linear and readable in the process.
I don't see a problem with squash merging, especially as a point of policy. It's been the best of both worlds in my experience.