Setup Husky to the project and configure Husky to run Git hooks

[yuramax]

We want to add commit hooks to Git with Husky to automate code tasks. This means that it would be nice if we could run all the necessary commands related to ESLint, Prettier, running jest tests, running Cypress tests before creating a Pull Request/commit.

Husky library - https://typicode.github.io/husky/

[killev]

I’m not sure that preventing commit code with problems fixes any issues. So i wouldn’t recommend to add husky

[yuramax]

@killev Peter, maybe we understand Husky differently, but our goal was to automate processes that can be forgotten. For example, developers forgot to run ES Lint, Prettier tests before committing, and when a PR is created, problems come up because for example tests/prettier/lint were not run locally before commit.

Perhaps there is another solution, if so, please advise. Thank you!

[killev]

@killev Peter, maybe we understand Husky differently, but our goal was to automate processes that can be forgotten. For example, developers forgot to run ES Lint, Prettier tests before committing, and when a PR is created, problems come up because for example tests/prettier/lint were not run locally before commit.

Perhaps there is another solution, if so, please advise. Thank you!

Let's treat the development process as collaborative experiments. E.g. you write some experimental code and ask colleagues to review it and offer adjustments or better solution. For that purpose you create a PR, mark is as a draft and commit any, even stupid code there.

From that point of view, it's absolutely fine if your code has problems in pipeline.

The main goal is not to allow weak/experimental code to get in main branch. We reach it be forbidding merge PRs with broken pipelines.