Please follow the following procedure when creating features to avoid unnecessary rejections:ĭo this the first time (Cloning & Forking): If you want to fix a new issue that's not listed there, create the issue, see if If you want to contribute code, start by looking at the open issues on. We prefer well named methods and code re-usability than a lot of comments.
Look and test your code well before submitting patches. If it's too hard to explain what you're doing, you're probably making things more complex than they already are.
When you submit a pull request try to explain what issue you're fixing in detail and how you're fixing in detail it so it's easier for us to read your patches.If you can include tests for your pull request you get extra bonus points ) We'll review your code and will only merge it to the master branch if it doesn't break the build. All pull requests should come from a feature branch created on your git fork.Try to follow our coding style and formatting before submitting a patch.If you want to help, the Issue tracker is a good place to take a look at.It'll be faster to code, and easier to maintain. ( DRY) Re-use your own code and our code.
0 kommentar(er)
