Repository Management

[Tohaker]

With multiple developers contributing, we should have some rules in place to ensure the main branch stays clean and tidy. I have some suggestions based on previous experience, very much open to discussion though;

• Require all Quality jobs to pass in CI before a PR can be merged
• Require Squash and merge as the only merge option
• Auto-delete branches after they've been merged
• Conventional Commits (Optional, works nicely with many automated tools such as Changelog generators)
• More detail in the CONTRIBUTING.md guidelines - there's plenty of examples in the community for this

[danstarns]

I totally agree with all these points.

Till now it's just been myself and so now it needs these listed to make it easier for everyone to contribute.

[danstarns]

I have added the necessary protection to the main branch and so now PRs require those checks.

Plus squash is now the only allowed option.

[Tohaker]

Added a new requirement - auto deleting branches after they've been merged. Helps keep the branches clean

[carbonrobot]

Since you are already using Github Actions, consider using Changests with its automated Github Action.