mirror of
https://github.com/Dolibarr/dolibarr.git
synced 2025-02-20 13:46:52 +01:00
f6fc93249d
# Qual: Lower severity on php-cs messages that should not block Some warning messages result in php-cs having an exit code of 2 and others only have an exit ocde of 1. When the exit code is 2, the warnings are fixable by php-cbf. In order to be able to filter on the warnings in the github ci flow, but still show them in the travis flow, I lower the level of the warnings that should not be blocking to 4. At the same time, the php-cs configuration in pre-commit now requires that the severity is minimum 5 to show the message (level 5 is the default for all warnings and errors). So this will limit the warning messages to the ones that should result in a failing ci action. If any new cases are discovered, they should also be lowered in the php-cs configuration file. |
||
|---|---|---|
| .. | ||
| apache | ||
| codesniffer | ||
| codetemplates | ||
| eclipse | ||
| fail2ban | ||
| git/hooks | ||
| multitail | ||
| nginx | ||
| phpunit | ||
| pre-commit | ||
| qodana | ||
| security | ||
| sonarqube | ||
| xdebug | ||
| README.md | ||
Setting up for Dolibarr development
Check out the online documentation for recommendations (to be updated).
If anything, install pre-commit - it will help run the tools to format and
make some basic verifications on your submission before committing and pushing
to github for a PR. See a quick start guide in this
Dolibarr repository.