-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
tagging releases #236
Comments
Humm yeah, I could, I simply have never needed to find the code of some older version... |
to be able to get the releases from github via just half of the reason for this is that the |
(putting tests in the sdist itself would allow for easy change-the-version-only upgrading too when using that source, of course, but it's nice to have symmetry between the repository and releases anyway, allowing someone to just click the tags in the ui here and see what is in what commit, diff two tags for changes, etc) |
It would also allow you to use |
Creating a new release tag from the GH UI is trivial. With the use of Actions you could even have the process automatically publish to pypi.org when you are ready to publish (although I do not have any experience with publishing to pypi myself). |
Hey @nekopsykose, |
yep, that would work great :) |
Done, from now on, every new release will include an automatic annotated tag! 👍 |
thank you very much! greatly appreciated :) |
You're welcome 👍 |
you currently publish releases to pypi: https://pypi.org/project/alive-progress/
these coincide with the version increments in
__init__.py
.however, it would also be nice to push tags to the repository when that is done, so they show up on github too, and it's possible to get e.g.
3.1.1
directly from the tags, instead of a commit hash.The text was updated successfully, but these errors were encountered: