[Feature] Git tag support in commits history #4742

New Issue

GiteaMirror · 2025-11-02T06:01:28-06:00

GiteaMirror commented

2025-11-02 06:01:28 -06:00

Originally created by @joseluisq on GitHub (Jan 28, 2020).

Gitea version (or commit ref): 1.10.3
Git version: N/A
Operating system: Linux x86_64
Database:
- PostgreSQL
- MySQL
- MSSQL
- SQLite

Description

It would great if Gitea can support git tags as well in commits history.

Screenshots

Current Gitea commits history:

[1] Here a visual example of Bitbucket Server commits history, note the tag aside.

Originally created by @joseluisq on GitHub (Jan 28, 2020).   - Gitea version (or commit ref): 1.10.3 - Git version: N/A - Operating system: Linux x86_64 - Database: - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite ## Description It would great if Gitea can support git tags as well in commits history. ## Screenshots Current Gitea commits history: <img width="739" alt="image" src="https://user-images.githubusercontent.com/1700322/73247318-ec233000-41b0-11ea-8f9d-79db9c1082a3.png"> [1] Here a visual example of Bitbucket Server commits history, note the tag aside. <img width="942" alt="image" src="https://user-images.githubusercontent.com/1700322/73246240-6c946180-41ae-11ea-9286-d73faa016efc.png">

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 06:01:28 -06:00

GiteaMirror closed this issue

2025-11-02 06:01:28 -06:00

GiteaMirror commented

2025-11-02 06:01:28 -06:00

@stale[bot] commented on GitHub (Mar 28, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 28, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:01:29 -06:00

@lunny commented on GitHub (Mar 28, 2020):

This feature is very useful.

@lunny commented on GitHub (Mar 28, 2020): This feature is very useful.

GiteaMirror commented

2025-11-02 06:01:29 -06:00

@bendem commented on GitHub (Jun 17, 2020):

That's one of the little things that make the overall experience better.

@bendem commented on GitHub (Jun 17, 2020): That's one of the little things that make the overall experience better.

GiteaMirror commented

2025-11-02 06:01:29 -06:00

@joseluisq commented on GitHub (Jun 17, 2020):

@bendem yeah!
Talking about subtle improvements, it can also be great if we can rename SHA1 to just Commit. Just a suggestion, but I think is not part of this feature issue.

@joseluisq commented on GitHub (Jun 17, 2020): @bendem yeah! Talking about subtle improvements, it can also be great if we can rename `SHA1` to just `Commit`. Just a suggestion, but I think is not part of this feature issue.

GiteaMirror commented

2025-11-02 06:01:29 -06:00

@lunny commented on GitHub (Jun 17, 2020):

Which place should we put the tags? Consider the most bad thing, one commit has been tagged as four tags.

@lunny commented on GitHub (Jun 17, 2020): Which place should we put the tags? Consider the most bad thing, one commit has been tagged as four tags.

GiteaMirror commented

2025-11-02 06:01:30 -06:00

@joseluisq commented on GitHub (Jun 17, 2020):

Which place should we put the tags?

Inside the Message table cell but aligned to right and overlying the message. See screenshot below.

Consider the most bad thing, one commit has been tagged as four tags.

Just displaying the number of tags greater than 1 for a particular commit.
Otherwise for one tag per commit, just display the tag as it is.

Here an example how is handled on Bitbucket server.

When mouse is over the "5 tags" label, a tooltip shows the 5 tags names concatenated by a separator.
Bitbucket is using a colon char like v1.4.4:v1.4:v1:latest:stable but Gitea can use a coma or another separator.

For Bitbucket, group of tags are not clickable, whereas for one tag per commit is possible to click on. But Gitea can take a different aproach, for example it can make clickable both kind of labels.
Group of tags can redirect to Tags page, whereas single tags can redirect to the corresponding tag page.

I hope this can help.

@joseluisq commented on GitHub (Jun 17, 2020): > Which place should we put the tags? Inside the _Message_ table cell but aligned to right and overlying the message. See screenshot below. > Consider the most bad thing, one commit has been tagged as four tags. Just displaying the number of tags greater than 1 for a particular commit. Otherwise for one tag per commit, just display the tag as it is. Here an example how is handled on Bitbucket server. ![image](https://user-images.githubusercontent.com/1700322/84947677-e344e380-b0ea-11ea-85bd-fab15cc0b62c.png) When mouse is over the _"5 tags"_ label, a tooltip shows the 5 tags names concatenated by a separator. Bitbucket is using a colon char like `v1.4.4:v1.4:v1:latest:stable` but Gitea can use a coma or another separator. For Bitbucket, group of tags are not clickable, whereas for one tag per commit is possible to click on. But Gitea can take a different aproach, for example it can make clickable both kind of labels. Group of tags can redirect to _Tags page_, whereas single tags can redirect to the corresponding _tag page_. I hope this can help.

GiteaMirror commented

2025-11-02 06:01:30 -06:00

@xblax commented on GitHub (Nov 17, 2023):

This feature would be really useful, I'm missing that a lot with Gitea. In other Git front ends that seems to be a standard feature, just like tags are also displayed together with the commit in standard git log or git log --pretty=oneline.

Any chance this feature could be considered for a future release?

@xblax commented on GitHub (Nov 17, 2023): This feature would be really useful, I'm missing that a lot with Gitea. In other Git front ends that seems to be a standard feature, just like tags are also displayed together with the commit in standard `git log` or `git log --pretty=oneline`. Any chance this feature could be considered for a future release?

GiteaMirror commented

2025-11-02 06:01:30 -06:00

@Richdark commented on GitHub (May 25, 2024):

This feature would truly enhance the experience. When using Bitbucket, a quick glance at commit history allows me to see where/when exactly has previous versions of my product been released. I'd love to have that option in Gitea too.

@Richdark commented on GitHub (May 25, 2024): This feature would truly enhance the experience. When using Bitbucket, a quick glance at commit history allows me to see where/when exactly has previous versions of my product been released. I'd love to have that option in Gitea too.

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