opensafely-core / opensafely-core/opencodelists
Enable newly enabled Ruff v0.16 rules that we currently ignore
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 60
- Forks
- 16
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 17
Description
Why are we doing this?
Ruff v0.16 has new rules that we currently fail validation on.
How will we know when it's done?
- When update-dependencies action PRs can succeed.
- We've enabled all the new Ruff rules.
What are we doing?
pin Ruff to v0.15 (probably least ideal)- set any ruleset exclusions that make sense
- fix all the remaining issues with the v0.16 default ruleset
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 locating the Ruff configuration and the update-dependencies action referenced in the issue, then run validation with Ruff v0.16 to identify remaining failures. Review the reported exclusions and code issues, and confirm the update-dependencies action can succeed when the checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100