Releases should show tag metadata when not overridden #1913

New Issue

GiteaMirror · 2025-11-02T04:17:41-06:00

GiteaMirror commented

2025-11-02 04:17:41 -06:00

Originally created by @clarfonthey on GitHub (Jun 10, 2018).

Gitea version (or commit ref): 1.4.2
Git version: 2.17.1
Operating system: Arch Linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Not relevant
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Description

Example: (dead link)

If you go and actually clone the repo, you'll find that the releases have separate messages from the commits they're attached to. It'd be nice if gitea could pull this data from git directly and show it as a release, so that it doesn't have to be stored in the database.

Originally created by @clarfonthey on GitHub (Jun 10, 2018). - Gitea version (or commit ref): 1.4.2 - Git version: 2.17.1 - Operating system: Arch Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - [x] Not relevant - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant ## Description Example: (dead link) If you go and actually clone the repo, you'll find that the releases have separate messages from the commits they're attached to. It'd be nice if gitea could pull this data from git directly and show it as a release, so that it doesn't have to be stored in the database.

GiteaMirror added the type/proposal type/enhancement labels 2025-11-02 04:17:41 -06:00

GiteaMirror commented

2025-11-02 04:17:41 -06:00

@0x5c commented on GitHub (Mar 15, 2019):

Yes, and/or tag annotations. It took me by surprise that Gitea didn't show the tag message as the release message. Especially since Gitea does not show releases separately from tags.

@0x5c commented on GitHub (Mar 15, 2019): Yes, and/or tag annotations. It took me by surprise that Gitea didn't show the tag message as the release message. Especially since Gitea does not show releases separately from tags.

GiteaMirror commented

2025-11-02 04:17:41 -06:00

@clarfonthey commented on GitHub (Mar 15, 2019):

Honestly, thinking about it more, release data really shouldn't be kept separate from git, minus the attachments. The tag should have all the release metadata.

@clarfonthey commented on GitHub (Mar 15, 2019): Honestly, thinking about it more, release data really shouldn't be kept separate from git, minus the attachments. The tag should have all the release metadata.

GiteaMirror commented

2025-11-02 04:17:41 -06:00

@0x5c commented on GitHub (Mar 15, 2019):

Indeed, just like Github currently does:

@0x5c commented on GitHub (Mar 15, 2019): Indeed, just like Github currently does: ![image](https://user-images.githubusercontent.com/5877043/54465203-59240780-4750-11e9-8420-38f8ab7ba214.png) ![image](https://user-images.githubusercontent.com/5877043/54465226-7f49a780-4750-11e9-84df-f0086dbaa5f8.png)

GiteaMirror commented

2025-11-02 04:17:42 -06:00

@clarfonthey commented on GitHub (Mar 15, 2019):

GitHub still doesn't handle this, actually; the release message is still separate from the tag message. IMHO they should be the same.

@clarfonthey commented on GitHub (Mar 15, 2019): GitHub still doesn't handle this, actually; the release message is still separate from the tag message. IMHO they should be the same.

GiteaMirror commented

2025-11-02 04:17:42 -06:00

@0x5c commented on GitHub (Mar 15, 2019):

Github seems to take the tag message as release note by default.
Unless I missed something. Let me check real-quick.

@0x5c commented on GitHub (Mar 15, 2019): Github seems to take the tag message as release note by default. *Unless* I missed something. Let me check real-quick.

GiteaMirror commented

2025-11-02 04:17:42 -06:00

@0x5c commented on GitHub (Mar 16, 2019):

Thinking about it (didn't have time to check yet), tags have other uses than only for releases. Maybe tags and releases should be separate (like on GitHub), but with a single button to make a release/note from a tag?

@0x5c commented on GitHub (Mar 16, 2019): Thinking about it (didn't have time to check yet), tags have other uses than *only* for releases. Maybe tags and releases should be separate (like on GitHub), but with a single button to make a release/note from a tag?

GiteaMirror commented

2025-11-02 04:17:42 -06:00

@clarfonthey commented on GitHub (Mar 16, 2019):

IMHO releases should be a strict subset of tags. i.e., you can have tags that aren't releases, but every release is a tag. Which tags are releases can be stored in the DB, but the release message should always be exactly the same as the tag message.

@clarfonthey commented on GitHub (Mar 16, 2019): IMHO releases should be a strict subset of tags. i.e., you can have tags that aren't releases, but every release is a tag. Which tags are releases can be stored in the DB, but the release message should always be exactly the same as the tag message.

GiteaMirror commented

2025-11-02 04:17:42 -06:00

@0x5c commented on GitHub (Mar 16, 2019):

Indeed
And if considering releases as a subset of tags is too much and non-acceptable (ie: opinions), at-least have the release note be, by default, the tag message.

@0x5c commented on GitHub (Mar 16, 2019): Indeed And if considering releases as a subset of tags is too much and *non-acceptable* (ie: opinions), at-least have the release note be, by default, the tag message.

GiteaMirror commented

2025-11-02 04:17:43 -06:00

@tfardet commented on GitHub (Sep 29, 2022):

If there is a desire to be able to keep tags and releases separate in some cases, would it be possible to:

give the user the ability to define a regex so that e.g. all vX.Y.Z tags are automatically considered releases
make the tags content the default release message?

It is a bit tedious to have to create releases from tags every time, then renter the text.

@tfardet commented on GitHub (Sep 29, 2022): If there is a desire to be able to keep tags and releases separate in some cases, would it be possible to: - give the user the ability to define a regex so that e.g. all ``vX.Y.Z`` tags are automatically considered releases - make the tags content the default release message? It is a bit tedious to have to create releases from tags every time, then renter the text.

GiteaMirror referenced this issue

2025-11-02 12:02:42 -06:00

[PR #1913] [MERGED] Fix ghost user bug #16117

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#1913