opensafely-core / opensafely-core/opensafely-cli
Migrate developer tooling to use `uv`
Open
Nobody has claimed this yet.
dx
- Dominant language
- Python
- Stars
- 2
- Forks
- 5
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 4
Description
We've modernised lots of our projects to use uv. I think it should be possible here too, even with the vendoring.
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 surveying the repository's developer-tooling configuration and vendoring setup to identify what currently needs migration. Confirm which tooling can use uv and define done as the relevant configuration and workflows consistently using uv without breaking vendored dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100