Use tag message to pre fill release details

[mjwwit]

Description

Currently, whenever a tag is pushed to Gitea, it creates an entry in "Releases". This entry does not contain any data besides the name of the tag. Tags though, like commits, allow for a message to be sent along with it. It would be awesome to see Gitea take advantage of this info and pre fill, for instance, the "Content" field of the new release entry.

[lunny]

I think this issue has gone since tags and releases is splited as two UI begin from v1.3. @mjwwit any idea?

[mjwwit]

@lunny I'm not really sure what you're talking about... I just created a tag using Gitea 1.3.1 and I still get an entry in the project Releases.

[nemoinho]

At least it would be awesome if you were able to edit this release to give it a meaningful content for the release-page afterwards.

Beside of that I would love the way @mjwwit had described.

[nemoinho]

Currently the workaround is one of the following two options:

Push tag and make release of it

1. Push a tag with message and name and whatever you need
2. Create a branch from the commit where the tag is annotated
3. Create a release from the created branch with the same name as the pushed tag and add a title and description

Create release and overwrite the generated tag

1. Create a release from a given branch
2. Fetch the tags
3. Delete the created tag locally and recreate it with all informations
4. Delete the tag remote on origin and push the locally created tag afterwards (the release will stay intact that way)

Both variants are kind of inconvenient and not user friendly.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[HarejJ]

I'm also having troubles by-passing the tag-release message field. The workarounds that @nemoinho posted are fine, but it would be really nice (and handy), that you could edit the release description (in UI) when posting a tag via git.

What is the status of this issue, is this going to be implemented? Or is this listed as a no-go?

[NiclasThobaben]

Any news on this one?