show tags in commit history

[SvenStaehs]

Select Topic Area

Product Feedback

Body

Request

In the Commit History page, I would like to see which commits are tagged, what is the name of the tag (and if it's an annotated tag, show the message when mouse hovers over the tag name)

For example, in this view, I would like to see that the top-most commit is tagged as v1.0.1:
https://github.com/github/docs/commits/a2f178351afc3ad570c5089a9deec80bc9e5f0e7
I can clearly see that tag relation if I open the commit itself, but want to see it in the history as well so I can easily see which commits were included in v1.0.0 and which commits are part of v1.0.1

See also:

• similar request in refined-git, implemented in 2019 (but I don't want to install tons of browser plugins on my work machine...)
• same feature is available in Azure DevOps

[rr-it]

The commit history timeline has dividers by date. How about adding dividers by tag:

[jason-berk-k1x]

I'm astonished this isn't just the default?!?!?! What am I missing??? Why, when you are looking at the commit history, would you NOT want to see the tagged commits. This is one case where Azure DevOps is better than GitHub

[ofer-pd]

I had to write my own CLI tool for this because GitHub doesn't provide this very basic, obvious, and essential view on history.

I don't get it.

[najibghadri]

This is so funny 🤣 🤣 🤣 The Github Desktop app has this feature but not the web Github commit history 🤣 🤣 🤣 COME ON GUYS! @github

[ofer-pd]

Thanks for the tip.

[ImanKCO]

The fact that even the broken BitBucket supports this and Github doesn't is beyond imagination. That should a relatively easy to add feature.

[kjpluck]

Adding my support to this very basic need.

[jjosenaldo]

+1, this would be pretty useful

[TechnicalFox]

IMHO this is expected functionality, and it's a shame it's not included in "enterprise" grade software. Personally I don't even need links or annotations, but the commit history page should not be missing default functionality from a standard "git log" call... That is to say; at the very least I expect the plaintext git tag names associated with each ref.

[rozalily]

This is also a feature in ADO, already. Though, don't take that as an endorsement of it...

[clar-gutierrez]

+1, please add this feature!

[mgollo]

We recently migrated hundreds of repos from discontinued Bitbucket server and this is really something I miss badly in GitHub!

[carlosmaranje]

Gitlab 1 - 0 Github

[chrissi-p-bosch]

Same her. Migrated form BB to GH and realy bad experience not to see tags next to commits

[smartin-fr]

Bumping -- will this be a thing?

[Niketin]

Please add this

[kandji-casey]

please add!

[SvenStaehs]

If you wish to show your interest in a feature, please upvote the post itself. AFAIK that's the metric GH team goes by, and writing "+1" comments just spams all the people who want to be notified about news on this topic 😉 Thank you for your interest!

[Top-Dev1219]

Adding tag visibility to the Commit History view would be a very useful improvement — especially for developers managing releases or maintaining multiple versions of a project. Tags are often used as lightweight release markers, so surfacing them directly in the commit list would make navigating a repo’s history much easier and more informative.

1. Why It’s Valuable

• Better release context:
  Seeing tags like v1.0.0, v1.0.1, etc., next to commits gives immediate context for what code changes belong to each release — without having to open each commit or check the “Tags” page separately.

• Improved traceability:
  Teams that follow semantic versioning or release automation can quickly correlate commits with deployment points. This helps when debugging regressions or comparing versions.

• Saves clicks:
  Right now, as you said, you can only see tags if you open the individual commit page - which interrupts the flow when browsing through history.

2. Suggested Implementation Details

• Show small tag labels (like colored badges) next to commits that have tags.

• On hover, display: Tag type (lightweight vs annotated), annotated tag message (if available), optionally, creation date and author.

• Could also include a filter (e.g., “Show only tagged commits”) for release review workflows.

3. Developer Experience Impact

• This feature would particularly help: Maintainers doing release audits, CI/CD engineers validating deployment triggers, Open-source contributors understanding project version flow

[chrisk314]

I have to switch back and forth between the commits view and the tags view to see which semver tag corresponds to which commit. Very poor UX. What an embarrassment to lack such a basic and obvious feature which is part of the standard git hist command output.

[sarev]

I'll just bump this one, as another year has passed... Now, where's that tumbleweed emoji?

[michael-masas-ctrl]

PLEASE ADD !!! THIS IS STILL RELEVANT

[nse-immeo]

Just do it.

[dbpieter]

Missing this feature from ADO.
Guess I'll have to do it the old school way: git log --all --decorate --graph --oneline

[yoshida-yuen-ijs]

Gitea can do this.
I was surprised that Github couldn't do this.