2016-12-29 13:35:36 +01:00
|
|
|
Contributing
|
|
|
|
|
============
|
|
|
|
|
|
|
|
|
|
First of all, **thank you** for contributing, **you are awesome**!
|
|
|
|
|
|
|
|
|
|
Here are a few rules to follow in order to ease code reviews, and discussions before
|
|
|
|
|
maintainers accept and merge your work.
|
|
|
|
|
|
2019-04-16 18:22:51 +03:00
|
|
|
You MUST follow the [PSR-1](http://www.php-fig.org/psr/psr-1/) and
|
|
|
|
|
[PSR-2](http://www.php-fig.org/psr/psr-2/). If you don't know about any of them, you
|
2016-12-29 13:35:36 +01:00
|
|
|
should really read the recommendations. Can't wait? Use the [PHP-CS-Fixer
|
|
|
|
|
tool](http://cs.sensiolabs.org/).
|
|
|
|
|
|
2020-12-10 21:59:36 +01:00
|
|
|
You MUST run the test suite (run `composer update`, and then execute `vendor/bin/simple-phpunit`).
|
2016-12-29 13:35:36 +01:00
|
|
|
|
|
|
|
|
You MUST write (or update) unit tests.
|
|
|
|
|
|
|
|
|
|
You SHOULD write documentation.
|
|
|
|
|
|
|
|
|
|
Please, write [commit messages that make
|
|
|
|
|
sense](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html),
|
|
|
|
|
and [rebase your branch](http://git-scm.com/book/en/Git-Branching-Rebasing)
|
|
|
|
|
before submitting your Pull Request.
|
|
|
|
|
|
|
|
|
|
Also, while creating your Pull Request on GitHub, you MUST write a description
|
|
|
|
|
which gives the context and/or explains why you are creating it.
|
|
|
|
|
|
|
|
|
|
Thank you!
|
