-
Notifications
You must be signed in to change notification settings - Fork 3
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 github release? #4
Comments
@endrebak ping on this again -- please consider doing this, it's a humble request. Actually, I maintain pyrle in Debian, and missing tags is a problem when I want to ship updated version of pyrle, hence this is a bit important for us (as downstream) and regular tagging would be awesome. |
Will do. I was ill and missed this
…On Sunday, October 24, 2021, NILESH ***@***.***> wrote:
@endrebak <https://github.com/endrebak> ping on this again -- please
consider doing this, it's a humble request.
Actually, I maintain pyrle in Debian, and missing tags is a problem when I
want to ship updated version of pyrle, hence this is a bit important for us
(as downstream) and regular tagging would be awesome.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEHURURWMNCBKHRL5L5YH23UIPLQJANCNFSM5C7F4ZAQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Now I think I have created one for NCLS, pyrle and pyranges :)
On Mon, Oct 25, 2021 at 11:58 AM Endre Bakken Stovner ***@***.***>
wrote:
… Will do. I was ill and missed this
On Sunday, October 24, 2021, NILESH ***@***.***> wrote:
> @endrebak <https://github.com/endrebak> ping on this again -- please
> consider doing this, it's a humble request.
>
> Actually, I maintain pyrle in Debian, and missing tags is a problem when
> I want to ship updated version of pyrle, hence this is a bit important for
> us (as downstream) and regular tagging would be awesome.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#4 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEHURURWMNCBKHRL5L5YH23UIPLQJANCNFSM5C7F4ZAQ>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like there has been a 0.0.33 release, but the latest (and only) release tagged is 0.0.31
Can you tag newer commits and fix accordingly?
CC: @endrebak
The text was updated successfully, but these errors were encountered: