open-telemetry / open-telemetry/opentelemetry-python-genai
Review group release workflow dist/wheels workflow step
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39
- Forks
- 63
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 175
Description
Review if using a shared sep to publish wheels is worth it compared to the matrix style we currently have.
I believe you can run this action once to upload many build wheel/sdists in the
packages-dir. I guess you could theoretically gather all the artifacts together and run once instead of in a matrix.
Maybe this was has some benefits though.
Originally posted by @aabmass in https://github.com/open-telemetry/opentelemetry-python-genai/pull/234#discussion_r3553980947
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 dist/wheels workflow step and the discussion in PR #234. Compare the current matrix-based publishing flow with the proposed shared step, then settle on and apply the preferred workflow approach. Done means the wheel and sdist publishing workflow is reviewed and the chosen behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, release
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100