opensafely-core / opensafely-core/opencodelists
Consider running CI code checks outside of Docker
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 60
- Forks
- 16
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 17
Description
For OpenCodelists, the checks are run inside Docker containers.
For job-server, the checks are run on the code directly. Which is preferable, I'm not entirely sure, but maybe it's worth keeping the process consistent between projects.
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
Compare OpenCodelists' current Docker-based checks with the job-server workflow in .github/workflows/main.yml. Start by tracing how checks are invoked in each project and determine which approach is preferable for consistency. Done means the preferred approach and the required scope of any workflow change are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, python
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100