simplifies release retrieval using git tags #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Hello, thanks for your PR! could you rebase on master and just confirm it works for you ? Thanks ! |
Member
Author
|
Hi, this was a simplified alternative to the pull request that was just merged. I don't know if you want to use curl + sorting or git tags? |
Contributor
|
Oh right, I guess using git tags is better. Please update this PR and I'll merge, just make sure the newest version is at the end of list-all output. IIRC, this line installs the last version in output. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a simple alternative to retreive releases from the git mirror as the
previous list-all command seems to be broken. It seems better to avoid
sorting as well, since git tags will be chronological.