Git Tagging
suggest changeIntroduction
Like most Version Control Systems (VCSs), Git
has the ability to tag
specific points in history as being important. Typically people use this functionality to mark release points (v1.0
, and so on).
Syntax
- git tag [-a | -s | -u < keyid >] [-f] [-m < msg > | -F < file >] < tagname > [< commit > | < object >]
- git tag -d < tagname >
- git tag [-n[< num >]] -l [–contains < commit >] [–contains < commit >]
[--points-at < object >] [--column[=< options >] | --no-column]
[--create-reflog] [--sort=< key >] [--format=< format >]
[--[no-]merged [< commit >]] [< pattern >…]
- git tag -v [–format=< format >] < tagname >…
Found a mistake? Have a question or improvement idea?
Let me know.
Table Of Contents