democritus-project / democritus-project/roadmap
Remove duplicate pypi upload conditions
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the [pypi upload conditions](https://github.com/democritus-project/d8s-dates/blob/36a99deceeae82938444da477a417f4b89237ea8/.github/workflows/pypi-publish.yml#L6) used in projects throughout democritus are deployed if either there is a tag or if there is a release published; update this to only upload to pypi if one of these conditions is met.
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 referenced .github/workflows/pypi-publish.yml at line 6, then search the Democritus projects for equivalent PyPI publishing workflows. Compare their tag and release conditions and clarify which single condition should control uploads; done means the duplicated workflow logic is removed consistently and the intended trigger is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100