These are unofficial tools, rather than officially supported product features, but we’ve tried to make them solid, easy to use, and you can change them.
Before writing code, please search for existing issues or [create a new issue][public-issues].
Thank you for finding an issue, our projects are open sourced to encourage your success and provide you a way to share improvements or repair issues you experience. Please review the following checklist before submitting a new issue.
- To prevent duplication, please [search for issues][public-issues] and make sure it doesn’t already exist
- Please provide the following information to help our contributors in resolving the issue:
- Operating System and version
- Programming language and version
- Exception, error or issue summary
- Recreation steps or use case summary
- Example data (if available, DO NOT INCLUDE YOUR API KEY OR ANY PERSONAL DATA)
- Expected result or desired functionality
- Any extra information you’d like to provide
- Please give your issue a meaningful name
- Please, no trolling or flaming comments on issues (counter-productive)
- Please follow/watch your issue. We expect you to take issue reporting as seriously as we do.
- Fork this repository
- Create a new branch named after the issue you’ll be fixing (include the issue number as the branch name, example: Issue in GH is #8 then the branch name should be ISSUE-8))
- Ensure validation passes
- Submit a new Pull Request applying your feature/fix branch to the develop branch of this repository