-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
hub-release option for overwrite on attach #2657
Comments
@DanySK Thanks for the feature request!
Is it an option for you to try to fetch an existing release first, then create one if missing? if hub release show TAG >/dev/null; then
hub release edit TAG -a FILE
else
hub release create TAG -a FILE
fi Existing release assets that match |
It does cover most of the cases indeed, yet if I need to re-upload a new version of the same file I can't do so. Is there any reason I should be consistent and use a single tool? |
That sounds weird to me. If I'm reading hub's implementation of Any reason why you couldn't just use |
Here is a build where the command fails, my understanding was that the artifact had been uploaded already. Anyway, no problem for me at using |
@DanySK Thanks for that info. It appears that there is a bug with re-uploading assets in hub. You may want to try gh instead. The
|
The problem I'm trying to solve:
I'd like to be able to use hub to refresh the artifacts for some existing release.
This is especially useful in CI, I'd like to be able to create a release if non existing, then upload the file if they are not there already, or if they are different than the ones produced by the latest CI run.
How I imagine hub could expose this functionality:
hub release edit -a FILE --overwrite TAG
The text was updated successfully, but these errors were encountered: