git/list[1] front-page[2] threads[3] people[4] search[5] about
 

gitk: visually indicate whether a tag exists on a remote

From
ASAdi Shavit <adishavit@gmail.com>
Date
Jul 9, 2025, 08:36 UTC
Message-ID
<CAEWUs4gEsASB3Fog2Zc5tEfACPURjHPqaS6e2XNWj0i50O-e5Q@mail.gmail.com>
In-Reply-To
<CAEWUs4iWwrOw4sXT9PhdccZyWtcvTgQfHDbeavTk-2kOdjUMdA@mail.gmail.com>
Hi all,
*Problem*

When browsing history in **gitk**, I often need to know whether a tag I see on a commit was:

  * fetched from a remote (and therefore shared with collaborators), or
  * created only in my local repository and not yet pushed.

For branches this distinction is obvious because gitk lists local and remote-tracking branch heads separately. Tags, however, are shown in a single list, so a locally added tag and one fetched from ­–‐say–‐ `origin` look identical. This can mislead users into thinking a tag is already published when in fact it is not.

*Proposed enhancement*

Add an opt-in visual cue that a tag also exists on at least one remote. Possible UI sketches (open for discussion):

  1. **Suffix** the tag label with the remote name in parentheses, e.g.
     `v1.2.3 (origin)`.
  2. **Colour** or style the tag differently (similar to how remote
     branches are blue vs. local green).
  3. **Tool-tip**: on hover, list the remotes that advertise the tag.
*Why this belongs in gitk*

gitk’s strength is that it gives an at-a-glance view of history. Making tags’ publication state equally transparent would save users a trip to the command line and reduce accidental “forgot to push the tag” issues.

Thanks for considering, and for maintaining gitk!

Best regards, Adi Shavit

Next: Chris Torek
Message 1 of 3 in “gitk: visually indicate whether a tag exists on a remote”
  1. Adi ShavitJul 9, 2025
  2. Chris TorekJul 9, 2025
  3. Marc BranchaudJul 9, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.