Ensure `pre-commit` linting is run in CI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14
- Forks
- 4
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 1
Description
In #38 , I noted that we don't have pre-commit linting running in CI.
I think I configured this via pre-commit.ci in the past, but maybe that broke with the repo move.
I intend to setup pre-commit.ci again, since it gives the nice autofixing commits.
I've seen some projects setup both that and a GitHub Actions job for this, but I don't quite understand the goals of that configuration. So I don't intend to do that.
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 checking the repository's pre-commit configuration and the pre-commit.ci setup after the repository move. Confirm that pre-commit.ci runs the configured linting hooks and produces autofixing commits; the issue is done when CI linting is restored without adding a separate GitHub Actions job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100