Replies: 3 comments
-
Husky hook will not run if Here's an updated workflow to run prettier on changed files:
|
Beta Was this translation helpful? Give feedback.
-
Update: Husky hook is fine. Ran prettier on main and only one file had an issue (modules/eslint-plugin/scripts/generate-config.ts). It looks like the issue could be related to the GitHub codespace environment. The extensions are installed automatically and prettier is a dev dependency so I don't get why the precommit could fail. Maybe, a high CPU usage issue again? Anytime you see a high CPU warning in a GitHub codespace something goes wrong. Running all tests at once always causes high CPU usage. |
Beta Was this translation helpful? Give feedback.
-
GitHub codespace high CPU usage causes the precommit hook to fail or not run correctly. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This has happened multiple times. I merge main and I have to clean up after the merge because the added code has formatting issues. Is the added code not being verified with husky? Should I use no-verify when I merge main? Is this documented in the contributing guide?
Beta Was this translation helpful? Give feedback.
All reactions