-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add automatic publish to PyPI workflow with automatic release note #34
Conversation
Codecov Report
@@ Coverage Diff @@
## master #34 +/- ##
==========================================
Coverage ? 100.00%
==========================================
Files ? 11
Lines ? 387
Branches ? 23
==========================================
Hits ? 387
Misses ? 0
Partials ? 0
Continue to review full report at Codecov.
|
d492f82
to
88d89ad
Compare
According to cjolowicz/cookiecutter-hypermodern-python#154, there is no need to have __version__ coputed at runtime by default. If users need it there are alternative ways to get it.
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.
Wow, very cool CI/CD 👍 🎉
Seems nice!
Added some label release propositions.
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.
Ups, some English corrections
Fix typo in comments Co-authored-by: Quentame <[email protected]>
Contributes to #18 |
The Release workflow publishes the package on PyPI. The workflow also creates a version tag in the GitHub repository, and publishes a GitHub Release using Release Drafter. The workflow is triggered on every push to the master branch.
Release steps only run if the package version was bumped. If the package version did not change, the package is instead uploaded to TestPyPI as a prerelease, and only a draft GitHub Release is created. TestPyPI is a test instance of the Python Package Index.