Why should I care about lightweight vs. annotated tags?

by

The big plus of an annotated tag is that you know who created it. Just like with commits, sometimes it’s nice to know who did it. If you’re a developer and you see that v1.7.4 has been tagged (declared ready) and you’re not so sure, who do you talk to? The person whose name is in the annotated tag! (If you live in a distrustful world, this also keeps people from getting away with tagging things they shouldn’t.) If you’re a consumer, that name is a stamp of authority: that’s Junio Hamano saying this version of git is hereby released.

The other metadata can be helpful too – sometimes it’s nice to know when that version was released, not just when the final commit was made. And sometimes the message can even be useful. Maybe it helps explain the purpose of that particular tag. Maybe the tag for a release candidate contains a bit of a status/to-do list.

Signing tags is pretty much like signing anything else – it provides one more level of security for the paranoid. Most of us aren’t ever going to use it, but if you really want to verify everything before you put that software on your computer, you might want it.

Edit:

As for what to write in a tag annotation, you’re right – there’s not always much useful to say. For a version number tag, it’s implicitly understood that it marks that version, and if you’re happy with your changelogs elsewhere, there’s no need to put one there. In this case, it’s really the tagger and date that are the most important. The only other thing I can think of is some sort of stamp of approval from a test suite. Have a look at git.git’s tags: they all just say something like “Git 1.7.3 rc1”; all we really care about is Junio Hamano’s name on them.

However, for less obviously named tags, the message could become much more important. I could envision tagging a specific special-purpose version for a single user/client, some important non-version milestone, or (as mentioned above) a release candidate with extra information. The message is then much more useful.

More Related Contents:

  1. How to delete a remote tag?
  2. How do you push a tag to a remote repository using Git?
  3. Download a specific tag with Git
  4. How can I get the latest tag name in current branch in Git?
  5. How is a tag different from a branch in Git? Which should I use, here?
  6. How can I move a tag on a git branch to a different commit?
  7. Does “git fetch –tags” include “git fetch”?
  8. What is git tag, How to create tags & How to checkout git remote tag(s)
  9. How do I delete a remote tag?
  10. How do you rename a Git tag?
  11. What is the difference between an annotated and unannotated tag?
  12. Remove local git tags that are no longer on the remote repository
  13. How to tell which commit a tag points to in Git?
  14. Depend on a branch or tag using a git URL in a package.json?
  15. How to list all Git tags?
  16. How do I edit an existing tag message in Git?
  17. How to clone a specific Git tag
  18. Do git tags get pushed as well?
  19. Git – Checkout a remote tag when two remotes have the same tag name
  20. Create a tag in a GitHub repository
  21. In git, how do I sync my tags against a remote server?
  22. How can I delete a remote tag?
  23. How to list all tags that contain a commit?
  24. What exactly do we mean by “branch”?
  25. git submodule tracking latest
  26. How do I resolve git saying “Commit your changes or stash them before you can merge”?
  27. Resetting remote to a certain commit
  28. Difference between “git checkout ” and “git checkout -​- “
  29. Git commit date
  30. git clean is not removing a submodule added to a branch when switching branches

Leave a Comment