labcodes / labcodes/django-react-boilerplate

Migrate from `husky` to `pre-commit`

Open
#36 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
45
Forks
6
PR merge metrics
No merged PRs in 30d

Description

pre-commit is a framework for managing and maintaining multi-language pre-commit (and others) git hooks

pre-commit supports run javascript code via https://pre-commit.com/#node
pre-commit supports create hooks for the git pre-commit, pre-merge-commit, pre-push, prepare-commit-msg, commit-msg, post-checkout, post-commit, post-merge:
https://pre-commit.com/#pre-commit-install
https://pre-commit.com/#confining-hooks-to-run-at-certain-stages

  • Create .pre-commit-config.yaml on repository root.
    The .pre-commit-config.yaml file should contain:
repos:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the repository's existing husky setup and README. Create the root .pre-commit-config.yaml, then use the linked eslint, black, and flake8 hook documentation to configure the listed hooks. Update the README with setup instructions and verify the configured hooks run as expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, javascript, python
Domain
developer-experience, documentation, tooling
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.