This document contains basic guidelines to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
- Fork the repo and create your branch from
master
. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Make sure your code lints.
- Issue your pull request.
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project.
Report bugs using issues
All bugs are tracked using GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
Great bug reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can.
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
All code should follow the PSR-12: Extended Coding Style
- 4 spaces for indentation rather than tabs
- Newlines after opening curly brackets in classes and methods
By contributing, you agree that your contributions will be licensed under its MIT License.