Git tag, Why this duplicate tag in remotes?

by

There are two types of tags in Git: “lightweight” and “annotated”.

Lightweight tags are simply refs in the refs/tags/ namespace that point to some other object. They are created by using git tag <tagname> [object] without -a, -m, -F, -s, or -u.

Annotated tags are actually a separate kind of Git object (a tag object) that point to some other object. Tag objects store committer information, author information, a message (similar to commit objects) and they point to any single other object (different from commit objects in that commits point to exactly one tree object and zero or more other commit objects).

When you have an annotated tag, you usually also have a ref that points to it. Technically this ref is itself a “lightweight” tag, but we usually do not describe them separately.

Normally, both kinds of tags point to commits, but they can point to any kind of Git object (tag, commit, tree, or blob). The git.git repository has refs/tags/junio-gpg-pub that points to a blob that contains the maintainer’s GPG public key. Also, torvalds/linux-2.6.git has refs/tags/v2.6.11 that points to a tree. Although tags that point to non-commit objects are technically allowed, they may break or confuse some tools, so they should be avoided, if possible.

The syntax ^{} suffix (described in gitrevisions(7)) is the tag dereferencing syntax (sometimes called the “peeled tag” syntax). For tag objects, it evaluates to the first non-tag object to which the tag object points (it will recursively deference a chain of tag objects until it finds a non-tag object). For non-tag objects, it means the same thing as without the ^{} suffix.

The refs/tags/Prod_Release_2.3 ref in your central repository points to the tag object named 30bd19ef190cf664356c715b56044ce739f07468.
That tag objects ultimately points to some other non-tag object named 4ae15ee04c2c41bfc7945e66f4effc746d52baec (probably a commit).

Thus, refs/tags/Prod_Release_2.3^{} resolves to 4ae15ee04c2c41bfc7945e66f4effc746d52baec.

More Related Contents:

  1. Git – Difference Between ‘assume-unchanged’ and ‘skip-worktree’
  2. Git, fatal: The remote end hung up unexpectedly
  3. How can I undo pushed commits using git?
  4. How can I make Sublime Text the default editor for Git?
  5. How can I merge two commits into one if I already started rebase?
  6. How do I ignore an error on ‘git pull’ about my local changes would be overwritten by merge?
  7. Git SSH error: “Connect to host: Bad file number”
  8. git, msysgit, accents, utf-8, the definitive answers
  9. Why doesn’t Git use more modern SHA?
  10. ‘git diff’ doesn’t show enough
  11. How can I tell if one commit is a descendant of another commit?
  12. How do I find and restore a deleted file in a Git repository?
  13. How do I create a remote Git branch?
  14. How can I calculate the number of lines changed between two commits in Git?
  15. Trying To Understand/Determine A Basic Git Workflow
  16. How to merge remote changes at GitHub?
  17. Push to origin from GitHub action
  18. Username and password in command for git push
  19. Is it possible to host a bare Git repository using Dropbox, to share code?
  20. fatal: does not appear to be a git repository
  21. Git is refusing to merge unrelated histories. What are ‘unrelated histories’?
  22. working with .git/info/exclude too late
  23. Editing the git commit message in GitHub
  24. Github (SSH) via public WIFI, port 22 blocked
  25. How do I manage conflicts with git submodules?
  26. Linking a single file from another git repository
  27. A Regex to match a SHA1
  28. How to display the tag name and branch name using git log –graph
  29. Why does zsh kills my process every time I enter a git command
  30. Git – Ignoring a specific modification to a config file

Leave a Comment