<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=5716) </details> <!--IssueSummary end--> It is reasonably common for projects to include Git hooks to help developers make sure code is linted before making a commit, and even to lint the commit message itself. Since we'll need to install dev dependencies to run tests, we should also run commit hooks too! ### Proposal Run Git hooks in the attached runner when committing: - `pre-commit` run after **Commit** is clicked after providing a commit message - `commit-msg` run after the `pre-commit` hook succeeds, and if successfully, push the commit. ### Links / references - Husky https://github.com/typicode/husky makes Git hooks easy for node projects