Skip to content

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

Description

@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.

Activity

  1. added
    bugSomething isn't working
    help wantedExtra attention is needed
    on Sep 24, 2026
  2. andrew commented on Sep 24, 2026

    @andrew
    Contributor

    thanks for reporting, pr over here: #167

  3. added 2 commits that reference this issue on Sep 24, 2026
    272b029
    45158b2
  4. added a commit that references this issue on Oct 5, 2026
    70caf18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions