Branching Model Team Agreement

[wenzowski]

A place to start on a few branching model team agreements to consider adopting:

• Be as lightweight as possible in our approach, and only focus on adopting team agreements that will add value to our future selves.
• Adopt the main branch as our default branch.
• Agree never to commit directly on main under any circumstances, and implement branch protection rules as a guardrail to enforce the agreement, including enforcement to administrators of this repo.
• Make draft pull requests early and often to facilitate a transparent process.
• Ruthlessly delete branches that aren't tied directly to an open pull request.
• Adopt Conventional Commits standard for commit messages, and consider authoring commit messages using Commitizen to make the spec easier while ensuring notes stay informative.
• Follow peer review best practices by suggesting opportunities to improve code during peer review, merging as soon as the code is better than the code in the target branch and release ready.
• Treat any opportunity for improvement feedback identified during peer review but not implemented in the PR where it was raised as technical debt worthy of a new issue referencing the PR where the comments first came up.
• Commit finalized agreements in docs/branching_model.md as a living document, to ensure any decision can be updated as and when required.

[kriscooke]

I would like to second each of these motions above ✅

[BCerki]

Thirded