Follow the “Conventional Commits” commit convention & allow only squashing when merging PRs unless specified otherwise

[itsWindows11]

Duplicates

• I have searched the existing issues

Summary 💡

See https://www.conventionalcommits.org/en/v1.0.0/ for more details.

In order to easily generate release notes on GitHub, we need to follow a commit convention like this one & additionally have a PR policy where only squashing is allowed unless stated otherwise for reasons where a merge or rebase is applicable (so we don't bloat the release notes).

Examples 🌈

Below are potential examples of commit messages, which can eventually add up together to be a valid release notes list:

• feat(blocks): add new block type.
• docs: April Fools update.

Motivation 🔦

No response