Use updated PHP-CS-Fixer in standard location #16
|
@ -2,10 +2,10 @@
|
||||||
#
|
#
|
||||||
# Checks the PHP CS syntax
|
# Checks the PHP CS syntax
|
||||||
#
|
#
|
||||||
if ! echo "${CHANGED_FILES}" | grep -qE "^(\\.php_cs(\\.dist)?|composer\\.lock)$"; then
|
if ! echo "${CHANGED_FILES}" | grep -qE "^(\\.php-cs-fixer(\\.dist)?\\.php|composer\\.lock)$"; then
|
||||||
EXTRA_ARGS=$(printf -- '--path-mode=intersection\n--\n%s' "${CHANGED_FILES}");
|
EXTRA_ARGS=$(printf -- '--path-mode=intersection\n--\n%s' "${CHANGED_FILES}");
|
||||||
else
|
else
|
||||||
EXTRA_ARGS='';
|
EXTRA_ARGS='';
|
||||||
fi
|
fi
|
||||||
|
|
||||||
./bin/dev/php-cs-fixer/vendor/bin/php-cs-fixer fix --config=.php_cs.dist -v --diff --diff-format=udiff --dry-run --using-cache=no ${EXTRA_ARGS}
|
./vendor/bin/php-cs-fixer fix -v --diff --dry-run --stop-on-violation --using-cache=no ${EXTRA_ARGS}
|
||||||
|
|||||||
|
|
Loading…
Reference in a new issue
The previous call used the
--dry-run
flag, I’m not sure we should remove it.I've changed the command from
fix --dry-run
tocheck
, so I think it's safe to omit the --dry-run flag. If you prefer, I can add it again.I've now adopted the suggestion from the php-cs-fixer documentation for running it on CI.