Reconsider `pre-commit` hooks
Open
Nobody has claimed this yet.
dev-tools
- Dominant language
- Python
- Stars
- 16
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
Reminder to myself to consider the following: Would it be good to add additionally hooks on push only (tests come to mind)? Should some current commit hooks be push hooks?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the repository's existing pre-commit configuration; the issue does not name a file or test. Determine which checks belong on commit versus push and define the resulting hook behavior as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100