UX: Tags and Releases operation #2143

New Issue

GiteaMirror · 2025-11-02T04:25:15-06:00

GiteaMirror commented

2025-11-02 04:25:15 -06:00

Originally created by @msg7086 on GitHub (Aug 4, 2018).

Gitea version (or commit ref): 1.5 nightly
Database:
- MySQL
Can you reproduce the bug at https://try.gitea.io:
- Yes

Description

We have tags and releases, just like what we found on GitHub. However they behave differently.

On GitHub, we are given a dropdown list to pick an existing tag, or an Edit Tag button to draft a release on existing tags. In Gitea, we have to type an existing tag manually. No link on an existing tag leads to draft a release for it.
On GitHub, a tag is a tag, a release is a release. Deleting a release has no harm to a tag. In Gitea, there's no way to revert the action of drafting a release for an existing tag. Whenever a release is deleted, the corresponding tag, even if it was created before, gets deleted as well. No alt option was given to the user.

Both behaviors bring discomfort to those who creates or deletes releases on the website for existing tags.

What's your opinion? Are they expected behaviors / by design? Shall those be improved in later versions?

Cheers

Originally created by @msg7086 on GitHub (Aug 4, 2018). - Gitea version (or commit ref): 1.5 nightly - Database: - MySQL - Can you reproduce the bug at https://try.gitea.io: - Yes ## Description We have tags and releases, just like what we found on GitHub. However they behave differently. 1. On GitHub, we are given a dropdown list to pick an existing tag, or an Edit Tag button to draft a release on existing tags. In Gitea, we have to type an existing tag manually. No link on an existing tag leads to draft a release for it. 2. On GitHub, a tag is a tag, a release is a release. Deleting a release has no harm to a tag. In Gitea, there's no way to revert the action of drafting a release for an existing tag. Whenever a release is deleted, the corresponding tag, even if it was created before, gets deleted as well. No alt option was given to the user. Both behaviors bring discomfort to those who creates or deletes releases on the website for existing tags. What's your opinion? Are they expected behaviors / by design? Shall those be improved in later versions? Cheers

GiteaMirror added the type/proposal label 2025-11-02 04:25:15 -06:00

GiteaMirror closed this issue

2025-11-02 04:25:15 -06:00

GiteaMirror commented

2025-11-02 04:25:16 -06:00

@lafriks commented on GitHub (Aug 6, 2018):

I think this can be improved

@lafriks commented on GitHub (Aug 6, 2018): I think this can be improved

GiteaMirror commented

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

@DjSni commented on GitHub (Aug 18, 2019):

There should also be a way to delete tags that have been pushed through git.
Also, there is no way to delete release assets. If the release is deleted, the assets will remain in the folder.

#677

@DjSni commented on GitHub (Aug 18, 2019): There should also be a way to delete tags that have been pushed through git. Also, there is no way to delete release assets. If the release is deleted, the assets will remain in the folder. #677

GiteaMirror commented

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

@lunny commented on GitHub (Aug 14, 2024):

I think this is outdated. So closing it.

@lunny commented on GitHub (Aug 14, 2024): I think this is outdated. So closing it.

GiteaMirror referenced this issue

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

[PR #2143] [MERGED] Fix SHA1 hash linking #16256

GiteaMirror referenced this issue

2025-11-02 12:07:55 -06:00

[PR #2293] [MERGED] Fix SHA1 hash linking (#2143) #16328

Sign in to join this conversation.