mirror of
https://github.com/ramsayleung/rspotify.git
synced 2026-04-26 07:55:55 +03:00
[GH-ISSUE #210] [meta] could you tag crate releases #70
Labels
No labels
Stale
bug
discussion
enhancement
good first issue
good first issue
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rspotify#70
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hhirtz on GitHub (May 8, 2021).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/210
Is your feature request related to a problem? Please describe.
I'm always frustrated when I want to find the commit from which
cargo publishwas called and I find out there's no tag for it. ':-)Describe the solution you'd like
Can you please
git tag v0.x.x && git push origin v0.x.xwhen you publish a version.Describe alternatives you've considered
No need to make a GitHub release, just a tag would work.
Additional context
https://git-scm.com/book/en/v2/Git-Basics-Tagging
@ramsayleung commented on GitHub (May 9, 2021):
Great point, thanks for your heads-up, I will tag the crate release when I release a new version in the future. It's my bad to forget to do so before :-)
@marioortizmanero commented on GitHub (May 9, 2021):
we should create a continuous deployment flow for github CI that automatically uploads everything to crates.io once a tag is published
@ramsayleung commented on GitHub (May 9, 2021):
I have pushed a PR to do so.