thunderbird / thunderbird/appointment
Setup pre-commit linter
Open
Nobody has claimed this yet.
maintenance
- Dominant language
- Python
- Stars
- 552
- Forks
- 29
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 23
Description
I dislike pre-commit linters, but I always forget to run them myself. My attempt at setting it on PR wasn't great, so let's just do it on pre-commit.
Contributor guide
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
Review the repository's existing pull-request lint setup and identify the entry point used for linting. Configure that check to run as a pre-commit hook, then verify that the linter runs before a commit and still passes on the repository's current code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100