Explain our use of Conventional Commits in CONTRIBUTING.md

[resir014]

Description

This repository uses the Conventional Changelog specification for our commit messages + Pull Request titles. Explain in the CONTRIBUTING.md file about how we use these commit messages.

Implementation model

The Conventional Changelog specification can be read here: https://www.conventionalcommits.org/en/v1.0.0/ - as a refresher:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

The commit types that we use are: feat, fix, refactor, docs, build, chore, perf, style, test. This follows the Angular commit message guidelines.

If possible, we should also define the scopes that this project uses.

Tasks

• Explain our use of Conventional Changelog specification
• Explain the commit types that we use
• Explain the use of commitlint to lint commit messages
• (Optional) Switch default merge type for PRs to squash merge-only, to ensure all commit messages match standards

[resir014]

Final task has already done through the GitHub repo settings.

We can update each PR's title with the appropriate conventional commit standards before triggering automerge.