π First of all, thanks for taking the time to contribute! π
We use github to host code, to track issues and feature requests, as well as accept pull requests.
Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
master
. - You should test the code you've added.
- Ensure that changes aligns with the community guideline and doucumentation
- Don't just open pull requests with minor text edits
- Issue that pull request!
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or less
- Reference issues and pull requests liberally after the first line
- When only changing documentation, include [ci skip] in the commit title
- Consider starting the commit message with an applicable emoji:
- π¨
:art:
when improving the format/structure of the code - π
:racehorse:
when improving performance - π±
:non-potable_water:
when plugging memory leaks - π
:memo:
when writing docs - π§
:penguin:
when fixing something on Linux - π
:apple:
when fixing something on macOS - π
:checkered_flag:
when fixing something on Windows - π
:bug:
when fixing a bug - π₯
:fire:
when removing code or files - π
:green_heart:
when fixing the CI build - β
:white_check_mark:
when adding tests - π
:lock:
when dealing with security - β¬οΈ
:arrow_up:
when upgrading dependencies - β¬οΈ
:arrow_down:
when downgrading dependencies - π
:shirt:
when removing linter warnings
- π¨
By contributing, you agree that your contributions will be licensed under its MIT License.