You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
We're closing this issue because it's inactive, already solved, old, or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.
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
The text was updated successfully, but these errors were encountered: