We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When the version is bumped with poetry version, we should automatically create a GH release and a PyPI release.
poetry version
Actually, I think maybe it'd be better to do this when tagging with git? Use something like poetry-dynamic-versioning.
So when we want to do a new version something like this?
main
Some links to investigate further:
https://github.com/softprops/action-gh-release https://keepachangelog.com/en/1.0.0/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When the version is bumped withpoetry version
, we should automatically create a GH release and a PyPI release.Actually, I think maybe it'd be better to do this when tagging with git? Use something like poetry-dynamic-versioning.
So when we want to do a new version something like this?
main
has the commits we want to include in the release.Some links to investigate further:
https://github.com/softprops/action-gh-release
https://keepachangelog.com/en/1.0.0/
The text was updated successfully, but these errors were encountered: