Lines Matching +full:pull +full:- +full:requests

5 -------------
11 -------------
22 -------------
32 Feature requests
33 -------------
35 Feature requests have to be labeled as such and have to include reasoning for the change in questio…
38 Pull requests
39 -------------
41 Pull requests should be always based on the default [development](https://github.com/mpdf/mpdf/tree…
46 * Use an aptly named feature branch for the Pull request.
47 * Only files and lines affecting the scope of the Pull request must be affected.
52 When updating a PR, do not create a new one, just `git push --force` to your former feature branch,…