Ensure existing codebase follows new practices in developer documentation
Open
Nobody has claimed this yet.
clean up
- Dominant language
- Python
- Stars
- 29
- Forks
- 9
- Avg merge
- 9d 9h
- Merged PRs (30d)
- 8
Description
Once https://github.com/CDCgov/multisignal-epi-inference/pull/224 is merged, we should revisit our existing code to make sure we follow our own guidance.
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
First review the developer documentation changes in pull request 224 and confirm whether that pull request is merged. Then inventory the existing Python code against the documented practices; the work is done when the relevant existing code follows that guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100