-
Notifications
You must be signed in to change notification settings - Fork 20
GitHub publish package to PyPI #71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR introduces a GitHub Action workflow to automate the deployment of the rispy package to PyPI and updates the README badges accordingly.
- Updated README.md to display PyPI status and download badges.
- Added .github/workflows/publish.yml to trigger deployments using GitHub Actions on tag push events.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| README.md | Updated PyPI badge presentation and added downloads badge |
| .github/workflows/publish.yml | Introduces workflow to deploy the package to PyPI |
|
Feel free to merge these PRs in the order you prefer. I don't wanna break anything. |
# Conflicts: # pyproject.toml
|
@J535D165 just cut a new release to confirm everything is working: https://github.com/MrTango/rispy/actions/runs/15215428334 One step closer to a v1.0... |
Add deployments to PyPI through GitHub Actions and trusted publishers. The workflow is currently set to release a package to PyPI whenever a tag
v*is applied to the repository.An example successful deployment is shown here:
After the successful testing, I switched to the production (not testing) PyPI deployment.