@jamieJamie Gaskins 
@fasterthanlimeamos I've had to do enough history spelunking that I value having the actual history of the work available to inspect - the idea of destroying that with squash or rebase is mildly horrifying in that context.
What's the security liability? intermediate commits with massive (or otherwise bad) files later deleted is all I can think of, and that's a good point.
@jugglerchrisChris Emerson @jamieJamie Gaskins @fasterthanlimeamos The security liability is that you can hide code changes in merge conflict diffs which do not show up in the history diff views without providing extra parameters.
Here’s a neat demonstration: https://tavianator.com/2025/sneaky.html
If you have a fediverse account, you can quote this note from your own instance. Search https://chaos.social/users/calisti/statuses/116023809363259958 on your instance and quote it. (Note that quoting is not supported in Mastodon.)