{"thread":{"id":"63768","subject":"gitk: visually indicate whether a tag exists on a remote","startedAt":"2025-07-09T08:37:10Z","lastAt":"2025-07-09T16:09:54Z","messageCount":3,"participants":["Adi Shavit","Chris Torek","Marc Branchaud"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"521628","messageId":"CAEWUs4gEsASB3Fog2Zc5tEfACPURjHPqaS6e2XNWj0i50O-e5Q@mail.gmail.com","threadId":"63768","inReplyTo":"CAEWUs4iWwrOw4sXT9PhdccZyWtcvTgQfHDbeavTk-2kOdjUMdA@mail.gmail.com","subject":"gitk: visually indicate whether a tag exists on a remote","fromName":"Adi Shavit","fromEmail":"adishavit@gmail.com","sentAt":"2025-07-09T08:36:43Z","receivedAt":"2025-07-09T08:37:10Z","isPatch":false,"sender":{"key":"adishavit@gmail.com","avatar":null},"body":"Hi all,\n\n*Problem*\n\nWhen browsing history in **gitk**, I often need to know whether a tag I\nsee on a commit was:\n\n  * fetched from a remote (and therefore shared with collaborators), or\n  * created only in my local repository and not yet pushed.\n\nFor branches this distinction is obvious because gitk lists local and\nremote-tracking branch heads separately.  Tags, however, are shown in a\nsingle list, so a locally added tag and one fetched from ­–‐say–‐\n`origin` look identical.  This can mislead users into thinking a tag is\nalready published when in fact it is not.\n\n*Proposed enhancement*\n\nAdd an opt-in visual cue that a tag also exists on at least one remote.\nPossible UI sketches (open for discussion):\n\n  1. **Suffix** the tag label with the remote name in parentheses, e.g.\n     `v1.2.3 (origin)`.\n  2. **Colour** or style the tag differently (similar to how remote\n     branches are blue vs. local green).\n  3. **Tool-tip**: on hover, list the remotes that advertise the tag.\n\n*Why this belongs in gitk*\n\ngitk’s strength is that it gives an at-a-glance view of history.  Making\ntags’ publication state equally transparent would save users a trip to\nthe command line and reduce accidental “forgot to push the tag” issues.\n\nThanks for considering, and for maintaining gitk!\n\nBest regards,\nAdi Shavit\n"},{"id":"521629","messageId":"CAPx1Gvd+XwN1YbbTiVCM-6rSr=9o5mB+T-=c8x5gpLkUp_hZ8A@mail.gmail.com","threadId":"63768","inReplyTo":"CAEWUs4gEsASB3Fog2Zc5tEfACPURjHPqaS6e2XNWj0i50O-e5Q@mail.gmail.com","subject":"Re: gitk: visually indicate whether a tag exists on a remote","fromName":"Chris Torek","fromEmail":"chris.torek@gmail.com","sentAt":"2025-07-09T08:45:16Z","receivedAt":"2025-07-09T08:45:30Z","isPatch":false,"sender":{"key":"chris.torek@gmail.com","avatar":"https://avatars.githubusercontent.com/u/16826774?v=4"},"body":"On Wed, Jul 9, 2025 at 1:37 AM Adi Shavit <adishavit@gmail.com> wrote:\n> When browsing history in **gitk**, I often need to know whether a tag I\n> see on a commit was:\n>\n>   * fetched from a remote (and therefore shared with collaborators), or\n>   * created only in my local repository and not yet pushed.\n\nThis information is not (currently) available in Git.\n\n> For branches this distinction is obvious because gitk lists local and\n> remote-tracking branch heads separately.  Tags, however, are shown in a\n> single list, so a locally added tag and one fetched from ­–‐say–‐\n> `origin` look identical.\n\nThey not only look identical, they *are* identical*.\n\nTo make these show up separately, you would have to do at least one of\nthe following:\n\n * collect information from the remote in gitk itself (run `git ls-remote`); or\n * collect information from the remote during `git fetch`\n\nThe latter would be possible by adding the concept of \"remote tags\" to\nGit, but this is a pretty big change (not technically difficult but\nprobably controversial).\n\nChris\n"},{"id":"521700","messageId":"5733c746-96dd-4375-8a68-5b42934ded45@xiplink.com","threadId":"63768","inReplyTo":"CAPx1Gvd+XwN1YbbTiVCM-6rSr=9o5mB+T-=c8x5gpLkUp_hZ8A@mail.gmail.com","subject":"Re: gitk: visually indicate whether a tag exists on a remote","fromName":"Marc Branchaud","fromEmail":"marcnarc@xiplink.com","sentAt":"2025-07-09T16:09:48Z","receivedAt":"2025-07-09T16:09:54Z","isPatch":false,"sender":{"key":"marcnarc@xiplink.com","avatar":"https://avatars.githubusercontent.com/u/14980203?v=4"},"body":"\nOn 2025-07-09 04:45, Chris Torek wrote:\n> \n>   * collect information from the remote during `git fetch`\n> \n> The latter would be possible by adding the concept of \"remote tags\" to\n> Git, but this is a pretty big change (not technically difficult but\n> probably controversial).\n\nThis was discussed long ago.  See:\n\nhttps://lore.kernel.org/git/201011040149.47968.johan@herland.net/\n\nand\n\nhttps://lore.kernel.org/git/CA+P7+xpj+8DZ=K0pna299Mu3nsQ4+JV_JUK=WFzzAFnJN+Bkbg@mail.gmail.com/\n\n\t\tM.\n\n"}]}