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
I wanted to use pretty-quick --check during CI to prevent that not formatted code is landing in master. But the --check property seems not to work correctly
pretty-quick version: 2.0.1
yarn pretty-quick
yarn run v1.22.4
$ \node_modules\.bin\pretty-quick
�🔍 Finding changed files since git revision 159bf55e4.
�🎯 Found 1 changed file.
✍️ Fixing up add-user.actions.ts.
✅ Everything is awesome!
Done in 3.02s.
PS yarn pretty-quick --check
yarn run v1.22.4
$ node_modules\.bin\pretty-quick --check
�🎯 Finding changed files since git revision 159bf55e4.
�🔍 Found 1 changed file.
✍️ Fixing up add-user.actions.ts.
✅ Everything is awesome!
Done in 2.47s.
--check and without check are doing the fixing but I just want to fail the job with --check flag
The text was updated successfully, but these errors were encountered:
Hey @elvirdolic. Are you still experiencing this? This isn't the expected behaviour at all. If you are able to gather some extra diagnostic info that would go a long way to solving your issue.
Hi,
I wanted to use pretty-quick --check during CI to prevent that not formatted code is landing in master. But the --check property seems not to work correctly
pretty-quick version: 2.0.1
--check and without check are doing the fixing but I just want to fail the job with --check flag
The text was updated successfully, but these errors were encountered: