QuTech-Delft / QuTech-Delft/libqasm
[CQT-88] Add a Publish to TestPyPI step to the release workflow
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 23
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Publishing to TestPyPI should catch errors in deployment a lot quicker.
- Just before publishing to PyPI we should publish to TestPyPI.
- The event triggering the publishing to TestPyPI is exactly the same as the event triggering the publishing to PyPI (when you create a new release in GitHub).
- If publishing to TestPyPI works, publishing to PyPI should also work.
- If publishing to TestPyPI fails, we avoid publishing to PyPI.
Contributor guide
No contributing guide indexed for this repository
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 locating the release workflow that publishes to PyPI and inspect its GitHub release trigger and publishing configuration. Add the TestPyPI publication immediately before the PyPI publication, ensuring a TestPyPI failure prevents the PyPI step; done when a release runs both steps in order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100