-
Notifications
You must be signed in to change notification settings - Fork 453
dbeaver/pro#6075 remove commit hooks #3548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
"version:set": "yarn workspaces foreach -Ap --include '@cloudbeaver/product-*' run version:set", | ||
"postinstall": "[ -z $CI ] && yarn lefthook install || true" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want to remove it completely, or should we just add a special command so only frontend developers can install it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I suggest to:
- Rename the command to something like
install-lefthook
so that yarn does not execute this command after installation of the deps - Add a VSCode task
- Add to the frontend guide that after all installations, we need to execute this task so the hook works for frontend devs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But before we do that, is there any chance to fix some config so the hook works only for frontend-specific files: ts, tsx, CSS, etc., but never throws anything for the backend developers?
cool! nice solution |
closes 6075
Special flags were added (merge, rebase) to disable pre-commit hooks during the merge and rebase stages. Postinstall script will be executed anyway due to issue so no need to keep it in the package json