Add "tags" to the commits page #12756

Closed
opened 2025-11-02 10:19:57 -06:00 by GiteaMirror · 8 comments
Owner

Originally created by @makar112233 on GitHub (Mar 28, 2024).

Feature Description

Hi.
Is it possible to add column "tags" to the "commits" page, like in a BitBucket?

Screenshots

image

Originally created by @makar112233 on GitHub (Mar 28, 2024). ### Feature Description Hi. Is it possible to add column "tags" to the "commits" page, like in a BitBucket? ### Screenshots ![image](https://github.com/go-gitea/gitea/assets/122980447/f35777b9-a0e6-4cc3-8e14-9a6f81b209c2)
GiteaMirror added the type/proposalproposal/accepted labels 2025-11-02 10:19:57 -06:00
Author
Owner

@silverwind commented on GitHub (Mar 28, 2024):

No dedicated table "column" please, just a right-aligned list of tags in the same column as the commit message.

@silverwind commented on GitHub (Mar 28, 2024): No dedicated table "column" please, just a right-aligned list of tags in the same column as the commit message.
Author
Owner

@makar112233 commented on GitHub (Mar 28, 2024):

@silverwind yes, your offer is better than mine.

@makar112233 commented on GitHub (Mar 28, 2024): @silverwind yes, your offer is better than mine.
Author
Owner

@delvh commented on GitHub (Mar 28, 2024):

Sounds good to me.
We should already offer the necessary route for it, ($REPO/commit/$SHA/load-branches-and-tags), so this might be a frontend only feature.
We can of course go the full fledged way and add a batched route that takes a number of commits at the same time and evaluates all of them, but I don't see that as a requirement for the first draft.
That way, all that needs to be done is getting a list of all commit SHAs to query, querying the route, and displaying the result.
It additionally has the benefit that the initial page load isn't affected by this as my guess is it might otherwise suffer a bit.

@delvh commented on GitHub (Mar 28, 2024): Sounds good to me. We should already offer the necessary route for it, (`$REPO/commit/$SHA/load-branches-and-tags`), so this might be a frontend only feature. We can of course go the full fledged way and add a batched route that takes a number of commits at the same time and evaluates all of them, but I don't see that as a requirement for the first draft. That way, all that needs to be done is getting a list of all commit SHAs to query, querying the route, and displaying the result. It additionally has the benefit that the initial page load isn't affected by this as my guess is it might otherwise suffer a bit.
Author
Owner

@silverwind commented on GitHub (Mar 28, 2024):

The question is thought whether we want to re-layout the commits table with flexbox first before attempting to extend the "mess" further 😆.

@silverwind commented on GitHub (Mar 28, 2024): The question is thought whether we want to re-layout the commits table with flexbox first before attempting to extend the "mess" further 😆.
Author
Owner

@makar112233 commented on GitHub (Apr 2, 2024):

Dear sirs, could you please, link this feature to some milestone, if it possible?

@makar112233 commented on GitHub (Apr 2, 2024): Dear sirs, could you please, link this feature to some milestone, if it possible?
Author
Owner

@delvh commented on GitHub (Apr 2, 2024):

I mean… PRs are always welcome

@delvh commented on GitHub (Apr 2, 2024): I mean… PRs are always welcome
Author
Owner

@silverwind commented on GitHub (Apr 2, 2024):

It would be quite hard to extend the current "fixed" commit table with such a right-aligned tag list. Better wait for the rewrite of that table to flexbox, then we can easily support such additions.

@silverwind commented on GitHub (Apr 2, 2024): It would be quite hard to extend the current "fixed" commit table with such a right-aligned tag list. Better wait for the rewrite of that table to flexbox, then we can easily support such additions.
Author
Owner

@kemzeb commented on GitHub (May 27, 2024):

Closing as this is a duplicate of #10036 and we currently have an open PR for it.

@kemzeb commented on GitHub (May 27, 2024): Closing as this is a duplicate of #10036 and we currently have an open PR for it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12756