crickets-and-comb/shared

Replace 3rd-party PyPi upload action with twine command

Open

#155 opened on Feb 24, 2026

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Makefile (0 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

We currently use a 3rd-party GitHub action, pypa/gh-action-pypi-publish@release/v1, in all of our CI_CD.yml workflows to upload our distribution to (Test)PyPi.

We should instead just use twine directly: twine upload --repository testpypi dist/*

Make it a reusable workflow or make recipe in shared.

Contributor guide

Research direction
Read the current CI/CD workflow files, understand how the publish step is configured, and implement a reusable workflow that uses twine to upload to TestPyPI.
Tech stack
pythongithub actions
Domain
devopsci cd
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonGitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75