| Server IP : 172.67.187.206 / Your IP : 172.71.28.155 Web Server : Apache/2.4.25 (Win32) OpenSSL/1.0.2j PHP/5.6.30 System : Windows NT WIN-ECQAAA40806 6.2 build 9200 (Windows Server 2012 Standard Edition) i586 User : SYSTEM ( 0) PHP Version : 5.6.30 Disable Function : NONE MySQL : ON | cURL : ON | WGET : OFF | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : /Inetpub/www/certificate/vendor/mpdf/mpdf/.github/ |
Upload File : |
Contributing ============ Issue tracker ------------- The Issue tracker serves mainly as a place to report bugs and request new features. Please do not abuse it as a general questions or troubleshooting location. For these questions you can always use the [mpdf tag](https://stackoverflow.com/questions/tagged/mpdf) at [Stack Overflow](https://stackoverflow.com/). * Please provide a small example in php/html that reproduces your situation * Please report one feature or one bug per issue * Failing to provide necessary information or not using the issue template may cause the issue to be closed without consideration. Pull requests ------------- Pull requests should be always based on the default [development](https://github.com/mpdf/mpdf/tree/development) branch except for backports to older versions. Some guidelines: * Use an aptly named feature branch for the Pull request. * Only files and lines affecting the scope of the Pull request must be affected. * Make small, *atomic* commits that keep the smallest possible related code changes together. * Code should be accompanied by a unit test testing expected behaviour. When updating a PR, do not create a new one, just `git push --force` to your former feature branch, the PR will update itself.