Discussion: whether to squash commits on merge by default

[andrewtavis]

Terms

• [X] I have searched open and closed issues
• [X] I agree to follow activist's Code of Conduct

Issue

A question that came up in discussion recently is whether with the new focus on code formatting, TS errors and getting everything checked with workflows we also would want to set the default merge for the repository as squashing commits into one. The commit history would thus be feature by feature and a bit more clear. I personally don't have a preference on this now, but do see value in us shifting to this in the future when we shift to a release based development cycle rather than deploying on commit with Netlify.

Generally how this will work is that the PR name will then be the commit message, and the comments for the PR will contain all the other commit messages for documentation.

Feedback on this would be welcome! This issue will be closed when we have made a decision, and if we do decide to squash on merge then this will need to be set in the settings.