-
Notifications
You must be signed in to change notification settings - Fork 82
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
Remove use of github-release #136
Remove use of github-release #136
Conversation
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Did you manage to test it out ?
Anyway, thanks for working on that. I wanted to do it a long time ago but didn't manage to actually work on it.
I tested with a repository of mine and it worked ok (including overwriting assets). I was wondering whether the
No problem! |
I'd say so for draft releases. Saves manually removing them when there's a
failure half way through.
…On Thu 18 Apr 2019, 16:55 Simon Pasquier, ***@***.***> wrote:
I tested with a repository of mine and it worked ok (including overwriting
assets). I was wondering whether the --overwrite flag is even needed,
maybe it is fine to always overwrite the assets for draft releases.
Anyway, thanks for working on that. I wanted to do it a long time ago but
didn't manage to actually work on it.
No problem!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#136 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABWJG5S33QDTHTDHKPDXHY3PRCDVTANCNFSM4HGTULPQ>
.
|
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
I've updated the PR so it will overwrite any asset file if the release is a draft. |
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
It has been found that the github-release program can leak credentials in the logs when it encounters an error. The upstream project itself isn't maintained actively, the original author recommends one of the forks but 1) it has the same issue and 2) it doesn't offer release binaries.
Looking at we needed from github-release, it isn't that complicated to use directly the GitHub API client instead of relying on an external program.
Closes #4.
Relates to #28 #26