Replies: 1 comment
-
You may have configured multiple remotes but for tags you and probably everyone else only follows one (main) repo, e.g. "origin", basically the integration remote. It makes sense to only fetch (remote) tags from this remote, e.g. the GitHub integration remote. By doing so we would see that the main repo is moving (i.e. publishes releases) before fetching from it. In the example pic we see exactly that: the "fork" of course has no additional tags but the origin has a new release I don't have fetched locally ("2.33.3"). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Maybe change the tags view to something like
T.i.
creatordate
); for temporary ("light") tags, the dates are actually not the "created" date but the committed date the tag points to. There is no working around here because for light tags git does not store such information.Note the mockup here uses
date:human
which is only available from git 2.21 on.Beta Was this translation helpful? Give feedback.
All reactions