Medical-Event-Data-Standard / Medical-Event-Data-Standard/MEDS-DEV
Committing results too quickly via issues results in action failures
Open
Nobody has claimed this yet.
priority:medium
Results storage and tracking
- Dominant language
- Python
- Stars
- 43
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/Medical-Event-Data-Standard/MEDS-DEV/actions/runs/15349229858/job/43192928395
Actions should be queued to only run one at a time somehow.
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 with the failed GitHub Actions run linked in the issue and trace it to the workflow configuration that launches on issue commits. Check how concurrent runs are handled, then make the workflow queue overlapping runs and verify that a repeated trigger no longer causes the reported failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100