NOTE: Contribution implies licensing under the terms of LICENSE (AGPL-3).
- Confirm the PR is against the
develop
branch. - Ensure commit messages follow the conventional commits style.
- Ensure commit messages adequately explain the reasons for the changes. outlined in the README.
- Run lint and prettier.
- Run the integration tests.
- Keep the first line short but informative.
- Provide explanation of why the change is being made in the commit message body.
- Prefer copying relevant information into the commit body over linking to them.
- Consider whether your commit message includes enough detail for someone to be able to understand it in the future.
- New branches are created on
develop
. - When complete new branches are merged to
develop
. - At release time,
develop
is merged intomain
.