Lines Matching +full:pull +full:- +full:requests
5 Before we can merge your Pull-Request here are some guidelines that you need to follow.
14 Your Pull-Request must be compliant with the said standard.
22 ## Unit-Tests
24 Please try to add a test for your pull-request. This project uses [PHPUnit](https://phpunit.de/) as…
26 You can run the unit-tests by calling `vendor/bin/phpunit`.
36 To test doc rendering before submitting your PR, you will need [Sphinx](http://www.sphinx-doc.org/e…
41 pip install --requirement doc/requirements.txt --user
47 cd doc && sphinx-build -W -b html -d _build/doctrees . _build/html
52 We automatically run your pull request through [Travis CI](https://www.travis-ci.org)
53 and [Scrutinizer CI](https://scrutinizer-ci.com/).
55 so please make sure that your code is working before opening up a Pull-Request.
60 Please try to avoid opening support-related tickets. For support related questions please use more …
68 Please allow us time to review your pull requests.
72 sense](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html),
73 and [rebase your branch](http://git-scm.com/book/en/Git-Branching-Rebasing)
74 before submitting your Pull Request.
77 commits](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)
78 too. This is used to "clean" your Pull Request before merging it (we don't want
81 Pull requests without tests most probably will not be merged.