CI: husky pre-commit already wired — decide whether to add a typecheck step
Open
Nobody has claimed this yet.
P3
wizard-pain
- Dominant language
- TypeScript
- Stars
- 197
- Forks
- 51
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 94
Description
Raw note from triage:
Lint for obvious dumb things pre-commit through husky maybe
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 existing Husky pre-commit configuration and the repository's package scripts. Determine whether a TypeScript typecheck belongs in the pre-commit flow, then verify the chosen behavior with the relevant local checks; the issue is done once that decision is implemented or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100