Skip to content
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

ci: add workflow to automatically release to PyPI and GitHub #93

Closed

Conversation

felix-seifert
Copy link
Collaborator

@felix-seifert felix-seifert commented Mar 18, 2024

Stack from ghstack (oldest at bottom):


  • This workflow gets automatically triggered on any tag push if the tag starts with v*.
  • This workflow builds and deploys the lib to PyPI with Twine.
  • After a successful deployment to PyPI, the workflow calls another workflow to issue a GitHub release.

[ghstack-poisoned]
felix-seifert added a commit that referenced this pull request Mar 18, 2024
* This workflow gets automatically triggered on any tag push if the tag starts with `v*`.
* This workflow builds and deploys the lib to PyPI with Twine.
* After a successful deployment to PyPI, the workflow calls another workflow to issue a GitHub release.

ghstack-source-id: 78173aef48deed2939943c5b8a20d6e64be00ce0
Pull Request resolved: #93
@felix-seifert
Copy link
Collaborator Author

Please just review the PR and DO NOT merge it!

@felix-seifert
Copy link
Collaborator Author

As mentioned in the discussions, the release workflow requires PyPI credentials. @csgoh Can you please persist the relevant secrets PYPI_USERNAME and PYPI_PASSWORD to make the needed credentials available to the release workflow?

@felix-seifert felix-seifert deleted the gh/felix-seifert/10/head branch March 18, 2024 06:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant