Medical-Event-Data-Standard / Medical-Event-Data-Standard/MEDS-DEV
Test code should only test datasets and/or tasks and/or models that have been changed since the last successful CI test run on GitHub.
Open
Nobody has claimed this yet.
help wanted
priority:critical
Testing
- Dominant language
- Python
- Stars
- 43
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
This is likely a reasonable approach strategy, in case anyone wants to try to tackle this: https://chatgpt.com/share/67c88eec-58dc-800c-9e32-40effb3ef690
Contributor guide
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 reviewing the repository's GitHub CI configuration and the linked strategy discussion. Identify how datasets, tasks, and models are represented and how the last successful CI run can be compared with current changes. Done means CI tests only components changed since that run, with coverage for the selection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, machine-learning, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100