0 comments (0 comments)2 reactions (2 reactions)0 assignees (0 assignees)Python4,574 stars (4,574 stars)553 forks (553 forks)batch import
Code qualityGood first issue
Description
Let's replace pre-commit with prek.
Contributor guide
- Tech stack
- python
- Domain
- developer experiencetooling
- Issue type
- chore
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 2
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-3 hours
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- fresh
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- Familiarity with Git hooksUnderstanding of pre commit configuration
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 70
- Research direction
- Check the current .pre commit config.yaml file in the repository to understand the existing hooks. Then review the prek documentation (https://github.com/j178/prek) to learn its configuration format and features. Compare the current hooks with prek equivalents, and create a pull request replacing the configuration file. Ensure the new configuration maintains the same linting and formatting hooks.