Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Git tag support in commits history #10036

Closed
1 of 4 tasks
joseluisq opened this issue Jan 28, 2020 · 8 comments · Fixed by #31082
Closed
1 of 4 tasks

[Feature] Git tag support in commits history #10036

joseluisq opened this issue Jan 28, 2020 · 8 comments · Fixed by #31082
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality
Milestone

Comments

@joseluisq
Copy link

  • 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:
image

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

image

@lunny lunny added the type/enhancement An improvement of existing functionality label Jan 28, 2020
@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Mar 28, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Mar 28, 2020
@stale stale bot removed the issue/stale label Mar 28, 2020
@lunny
Copy link
Member

lunny commented Mar 28, 2020

This feature is very useful.

@bendem
Copy link

bendem commented Jun 17, 2020

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

@joseluisq
Copy link
Author

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

@lunny
Copy link
Member

lunny commented Jun 17, 2020

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

@joseluisq
Copy link
Author

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

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.

@xblax
Copy link

xblax commented 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?

@Richdark
Copy link

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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants