We love your input! We want to make contributing to this project as easy and transparent as possible.
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.
To purpose a code change do the following:
- Fork the repo and create your branch from
develop
. - If you've added code that should be tested, add tests.
- If you've changed something, that should be documented, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
- If there is any feedback in pull request, do the necessary changes or explain why you did something in a way you did.
- If everything is good, a maintainer will merge your pull request, and the code will be included in the next release.
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 with detailed description!
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can (eg. shell script).
- 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)
People love thorough bug reports. I'm not even kidding.
- Make sure there are no
gofmt
issues - Make sure your coding style complies with already existing code
By contributing, you agree that your contributions will be licensed under its MIT License.