This repository has been archived by the owner on May 5, 2024. It is now read-only.
Uploading artifacts that don't exist doesn't cause an error #62
Labels
Comments
|
I see why this is happening. It's because a glob is being used and the blog can report no elements. I think that it would be more intuitive to have a behavior similar to Unix tools like |
eyal0
added a commit
to eyal0/actions
that referenced
this issue
Jan 5, 2021
eyal0
added a commit
to eyal0/actions
that referenced
this issue
Jan 5, 2021
eyal0
added a commit
to eyal0/actions
that referenced
this issue
Jan 6, 2021
eyal0
added a commit
to eyal0/actions
that referenced
this issue
Mar 23, 2021
marvinpinto
pushed a commit
that referenced
this issue
Mar 23, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I mistakenly didn't spell an artifact file correctly in the
filesargument to action-automatic-releases. I expected that there would be an error but instead, nothing happened and no assets were uploaded.The text was updated successfully, but these errors were encountered: