-
Notifications
You must be signed in to change notification settings - Fork 118
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
RFE: please start making github releases #149
Comments
Every release is tagged, but manually creating the releases from the web interface looks like a lot of busywork. |
example create release from tag using github action is shown in:
https://github.com/maarten-boot/test-scan-only/blob/main/.github/workflows/create-release.yml
…On Sun, 30 Jul 2023 at 23:39, rfc1036 ***@***.***> wrote:
Every release is tagged, but manually creating the releases from the web
interface looks like a lot of busywork.
Maybe somebody can contribute some automation?
—
Reply to this email directly, view it on GitHub
<#149 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACU73CXJNRCQWQ7OAUGGJA3XS3ICDANCNFSM6AAAAAA25MDAWI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Here is updated list of links which provides more details about automating process of crate gh release |
Sorry, but I do not care enough to spend my time implementing this. If anybody wants released tarballs then please submit a complete patch. |
To implement automated gh release it needs to be somewhere implanted release proces to add necessary modifications.
This RFE has nothing to to with any tar balls. |
https://github.com/rfc1036/whois/releases
Is it possible next time on release new version make the github release to have entry on https://github.com/rfc1036/whois/releases? 🤔
I'm asking because only on make gh release is spread notification about new release to those who have set watch->releases.
More about gh releases is possible to find on
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
The text was updated successfully, but these errors were encountered: