Use tag message to pre fill release details #288

New Issue

GiteaMirror · 2025-11-02T03:17:24-06:00

GiteaMirror commented

2025-11-02 03:17:24 -06:00

Originally created by @mjwwit on GitHub (Jan 26, 2017).

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.

Originally created by @mjwwit on GitHub (Jan 26, 2017). ## 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.

GiteaMirror added the hacktoberfest issue/confirmed type/feature labels 2025-11-02 03:17:24 -06:00

GiteaMirror commented

2025-11-02 03:17:24 -06:00

@lunny commented on GitHub (Dec 12, 2017):

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

@lunny commented on GitHub (Dec 12, 2017): I think this issue has gone since tags and releases is splited as two UI begin from v1.3. @mjwwit any idea?

GiteaMirror commented

2025-11-02 03:17:25 -06:00

@mjwwit commented on GitHub (Dec 12, 2017):

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

@mjwwit commented on GitHub (Dec 12, 2017): @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.

GiteaMirror commented

2025-11-02 03:17:25 -06:00

@nemoinho commented on GitHub (May 3, 2018):

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 commented on GitHub (May 3, 2018): 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.

GiteaMirror commented

2025-11-02 03:17:25 -06:00

@nemoinho commented on GitHub (May 15, 2018):

Currently the workaround is one of the following two options:

Push tag and make release of it

Push a tag with message and name and whatever you need
Create a branch from the commit where the tag is annotated
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

Create a release from a given branch
Fetch the tags
Delete the created tag locally and recreate it with all informations
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.

@nemoinho commented on GitHub (May 15, 2018): 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.

GiteaMirror commented

2025-11-02 03:17:25 -06:00

@stale[bot] commented on GitHub (Jan 26, 2019):

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.

@stale[bot] commented on GitHub (Jan 26, 2019): 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.

GiteaMirror commented

2025-11-02 03:17:26 -06:00

@HarejJ commented on GitHub (Oct 12, 2020):

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?

@HarejJ commented on GitHub (Oct 12, 2020): 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?

GiteaMirror commented

2025-11-02 03:17:26 -06:00

@NiclasThobaben commented on GitHub (Jun 30, 2021):

Any news on this one?

@NiclasThobaben commented on GitHub (Jun 30, 2021): Any news on this one?

GiteaMirror commented

2025-11-02 03:17:26 -06:00

@mic4ael commented on GitHub (Oct 1, 2024):

Is this still something you are considering to fix? If so, I would be happy to look into that and make my first contribution.

@mic4ael commented on GitHub (Oct 1, 2024): Is this still something you are considering to fix? If so, I would be happy to look into that and make my first contribution.

GiteaMirror referenced this issue

2025-11-02 11:43:09 -06:00

[PR #288] [MERGED] Docker integration #15286

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#288