`forge release create` produces unhelpful/generic error messages that make debugging release failures nearly impossible (Forgejo)

[defect-track]

Using forge against Forgejo to create releases results into vague or misleading error messages if things go wrong. The favorite errors are Error: Release has no Tag or Error: '' which are not very helpful. In most cases this happens if the TAG exists in the repository or a malformed tag is send.

You can work around it by always delete the tag first or check if it exists but until you reach that point it took me a couple of iterations ;-)

I haven't tracked it down further if this is a ForgeJo API issue or a forge wrapper issue. Might do it if time permits.

[andrew]

thanks for reporting, pr over here: #167