You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There aren't tests around this, what I'm gathering is that e.g. if we use the tag prefix of 'v', so version 1.2.3 has the tag v1.2.3,
avakas show output: 1.2.3
avakas set output: Version set to 1.2.3
avakas update output: Version updated from 1.2.3 to 1.2.4
is what is wanted. However, some of the code strips out the tag prefix, and others don't.
There's some uneven handling broadly, but do we have a preference for displaying the tag prefix in the CLI? If the answer is yes, the above would instead look like:
avakas show output: v1.2.3
avakas set output: Version set to v1.2.3
avakas update output: Version updated from v1.2.3 to v1.2.4
Super agnostic about this, just realized that I had some missing test coverage, and while I was looking at that, realized I had put no thought into how the tag prefixes might be handled
The text was updated successfully, but these errors were encountered:
There aren't tests around this, what I'm gathering is that e.g. if we use the tag prefix of
'v'
, so version 1.2.3 has the tagv1.2.3
,avakas show output:
1.2.3
avakas set output:
Version set to 1.2.3
avakas update output:
Version updated from 1.2.3 to 1.2.4
is what is wanted. However, some of the code strips out the tag prefix, and others don't.
There's some uneven handling broadly, but do we have a preference for displaying the tag prefix in the CLI? If the answer is yes, the above would instead look like:
avakas show output:
v1.2.3
avakas set output:
Version set to v1.2.3
avakas update output:
Version updated from v1.2.3 to v1.2.4
Super agnostic about this, just realized that I had some missing test coverage, and while I was looking at that, realized I had put no thought into how the tag prefixes might be handled
The text was updated successfully, but these errors were encountered: