Development practices

List of the development practices to follow in this project

GitHub issue

First step is always to create a GitHub issue, with a clear title and a body that explains precisely what is the bug or the feature described

Branch name

When creating a branch to solve an issue, use the naming convention <issue number>-description-of-the-change. So for example : #18-presist-test-results

Pull Request

Create a pull request for the branch that you created. The title should start with feat: or fix: or doc: or refactor: , then a very brief description.

The body should be a more thorough description. Always add Closes #<issue-number> at the end of the PR body.

Merging

Merging should always be done by squash and rebase. The use of any other merge method if squash and rebase is somehow not the best strategy for a PR should be discussed in the PR.