We are eternally grateful to you for wanting to contribute to this project. In order to make sure everything goes smootly, make sure you follow the below guidelines.
These guidelines were inspired by Ruby on Rails guidelines.
First, ensure the bug was not already reported by searching on GitHub under Issues. If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
First, Make sure that you follow the general coding conventions of the project. Open a new GitHub pull request with the patch. Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
That's great, but unless the refactor is very important and it is immensely useful, we cannot accept it. It simply takes too much time to ensure everything is working as intended.
Open up a new issue with your proposed feature. If it is too out-of-scope for this project, chances are we don't have the time or motivation to add it. But never hesitate to speak your mind!
If your contribution does not fit into these guidelines, don't hesitate to contact us.