FM / php_codesniffer

/var/www/vhosts/ihelp.ro/httpdocs/vendor/squizlabs/php_codesniffer/

/var/www/vhosts/ihelp.ro/httpdocs/vendor/squizlabs/php_codesniffer

Name	Size	Mode	Actions
bin/	-	0755	rm
src/	-	0755	rm
tests/	-	0755	rm
autoload.php	11887	0644	edit dl rm
CodeSniffer.conf	135	0644	edit dl rm
CodeSniffer.conf.dist	188	0644	edit dl rm
composer.json	1110	0644	edit dl rm
CONTRIBUTING.md	638	0644	edit dl rm
licence.txt	1540	0644	edit dl rm
phpcs.xsd	7054	0644	edit dl rm
README.md	6605	0644	edit dl rm

Edit: /var/www/vhosts/ihelp.ro/httpdocs/vendor/squizlabs/php_codesniffer/CONTRIBUTING.md (638B)

Contributing ------------- Before you contribute code to PHP\_CodeSniffer, please make sure it conforms to the PHPCS coding standard and that the PHP\_CodeSniffer unit tests still pass. The easiest way to contribute is to work on a checkout of the repository, or your own fork, rather than an installed PEAR version. If you do this, you can run the following commands to check if everything is ready to submit: cd PHP_CodeSniffer php bin/phpcs Which should display no coding standard errors. And then: phpunit Which should give you no failures or errors. You can ignore any skipped tests as these are for external tools.