The following is a set of guidelines for contributing to this project. We really appreciate that you are considering contributing!
Follow our Installation Guide to get this project up and running.
To report a bug, open an issue on GitHub with the label bug
using the available bug report issue template. Please ensure the bug has not already been reported. If the bug is a potential security vulnerability, please report it using our security policy.
To suggest a feature or enhancement, please create an issue on GitHub with the label enhancement
. Please ensure the feature or enhancement has not already been suggested.
- Fork the repo, create a branch, implement your changes, add any relevant tests, submit a PR when your changes are tested and ready for review.
- Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing before submitting a PR.
- If possible and/or relevant, use the Conventional Commits format when writing a commit message, so that changelogs can be automatically generated
- Follow the guidelines of writing a good commit message as described here https://chris.beams.io/posts/git-commit/ and summarised in the next few points:
- In the subject line, use the present tense ("Add feature" not "Added feature").
- In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...").
- Limit the subject line to 72 characters or less.
- Reference issues and pull requests liberally after the subject line.
- Add more detailed description in the body of the git message (
git commit -a
to give you more space and time in your text editor to write a good message instead ofgit commit -am
).