Add TAGS as range parameter, fixes #488 fixes #1027#1418
Merged
HaoZeke merged 1 commit intoairspeed-velocity:mainfrom May 20, 2025
Merged
Add TAGS as range parameter, fixes #488 fixes #1027#1418HaoZeke merged 1 commit intoairspeed-velocity:mainfrom
HaoZeke merged 1 commit intoairspeed-velocity:mainfrom
Conversation
timkpaine
force-pushed
the
tkp/tags
branch
2 times, most recently
from
9f75f8a to
d655133
Compare
Contributor
|
Rebased off main to get an updated CI, and merked ready for review. I think this is a nice feature. |
HaoZeke
approved these changes
May 20, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
ref: #488
ref: #1027
Adds a new supported range_spec
TAGSwhich will just list the tags of the repo and run on those.Don't just list and sort the tags, make sure they are reverse-chronologically sorted. Right now they are alphabetically sorted (which isn't even version-sorted, so not great)Running for this repo I get:
['v0.6.3', 'v0.6.2', 'v0.6.1', 'v0.6.0', 'v0.4.2', 'v0.4.1', 'v0.3.1', 'v0.3', 'v0.3b1', 'v0.2.2', 'v0.2.2rc1', 'v0.2.1', 'v0.2', 'v0.2rc2', 'v0.1.1', 'v0.1', 'v0.1rc3', 'v0.1rc2', 'v0.1rc1', 'v0.5.1', 'v0.5', 'v0.4', 'initial'], which matches the output ofgit tag -l --sort=taggerdateand so looks good