If you would like Pint to fix any files with code style errors but also exit with a non-zero exit code if any errors were fixed, you may use the --repair option:
./vendor/bin/pint --repair
However after creating a project with Laravel Breeze, this is the behavior I experience:
--test correctly signals a formatting error and exits
Pint Version
1.17.0
PHP Version
8.2.2
Description
According to the docs :
If you would like Pint to fix any files with code style errors but also exit with a non-zero exit code if any errors were fixed, you may use the --repair option:
./vendor/bin/pint --repair
However after creating a project with Laravel Breeze, this is the behavior I experience:
./vendor/bin/pint --test
FAIL .............................................................................................................................................. 46 files, 1 style issue
⨯ routes/auth.php
./vendor/bin/pint --repair
FIXED ....................................................................................................................................... 46 files, 1 style issue fixed
✓ routes/auth.php
I think I should see a big red X in the last row instead of the green tick.
Steps To Reproduce