Currently, this action attempts to create a new release with assets and falls back to uploading to an existing release. Even if the call to gh release create fails, GitHub creates a draft release with assets attached.
Example
In [gabe565/gh-profile](https://github.com/gabe565/gh-profile), I created release v1.1.0 in the web UI. The action runs and logs the following:
But a draft release is created:
This PR modifies this behavior by checking if a release exists first. If it does, gh release upload is called. Else, gh release create is called.
jef
commented
2 years ago
Currently, this action attempts to create a new release with assets and falls back to uploading to an existing release. Even if the call to
gh release createfails, GitHub creates a draft release with assets attached.Example
In [gabe565/gh-profile](https://github.com/gabe565/gh-profile), I created release v1.1.0 in the web UI. The action runs and logs the following:  But a draft release is created: This PR modifies this behavior by checking if a release exists first. If it does,
gh release uploadis called. Else,gh release createis called.