Creating tags from the command line…<\/p>\n
Tags allows us to store a pointer to the repository at a point in time, these are often used for “tagging” a release, but can be used for other purposes.<\/p>\n
Note: I will use the tag name v1.0.2 here, obviously this should be replaced with the tagname you’ve used\/assigned.<\/em><\/p>\n Listing your tags<\/strong><\/p>\n To see what tags you currently have on a repository run<\/p>\n this will list all your tags. <\/p>\n Creating your tags<\/strong><\/p>\n There’s a couple of ways to create your tags, the first is the annotated tag<\/p>\n Here we use -a (annotate) to create a new tag and -m (add a message). When creating an annotated tag, a message is expected and so you will be prompted to enter a message if you omit -m. Annotated tags store the message (although you could specify an empty message) along with the author of the tag. <\/p>\n Lightweight tags are another way to tag, these tags store no data with the tag (so do not supply -a or -m), for example<\/p>\n These tags store the commit checksum and whereas you’d tend to use the annotated tag for releases (for example) the lightweight tag might be used simply to label certain commits.<\/p>\n We can also tag by using the commit checksum (the 6a0b83 in the example below), this example uses a lightweight tag <\/p>\n Pushing your tags<\/strong><\/p>\n Ofcourse, if we’re working with others we’ll want to share our tags, so if we have a remote to push to then we can push the tag using<\/p>\n A simple git push<\/em> does not push our tags, we need to be explicit or we can use the –tags<\/em> switch to push all tags.<\/p>\n Viewing your tag<\/strong><\/p>\n We’ve seen that git tag<\/em> will list the tags but what about showing us the annotation tag data or what the tag actually refers to, this is where we use<\/p>\n If it’s an annotated tag you see the author of the tag and any message along with the last commit within that tag, for the lightweight we simply see the last commit details.<\/p>\n If you’ve signed your tag (see Signing tags<\/strong> below) you’ll also see the GPG signature attached to the tag.<\/p>\n Deleting your tag<\/strong><\/p>\n To delete a tag just use the following<\/p>\n If you’ve pushed your tag to a remote then use the following after the local delete<\/p>\n Or use<\/p>\n Checking out a tag<\/strong><\/p>\n We can checkout the tag just like any branch using<\/p>\n This will put your repository into a “detached HEAD” state. You cannot commit to this tag, or to put it another way, if you commit to this tag your commits will not appear within the tag, instead they’ll only be reachab;e by the commit hash.<\/p>\n If you intention it to make changes to a tag then instead, you need to branch from the tag, i.e.<\/p>\n Signing tags<\/strong><\/p>\n Tags can be signed using GPG. The purpose of this functionality is to simply ensure that the tag was created by the person we expected. I’ve not so far needed to sign a tag (or commits for that matter, which can also be signed). However there may be a time when this is useful, so let’s go through it.<\/p>\n To check if you have a key installed type<\/p>\n If no keys exist it’ll create the folders needed for creating keys. <\/p>\n To generate a key key run<\/p>\n This will ask for your “real name” and “email address”, followed by a pass phrase and then this will create your key. Now running gpg –list-keys<\/em> should list the newly created key.<\/p>\n Next we need to tell git to use our key using the following<\/p>\n where 123456789 is replaced by the pub<\/em> string associated with your key (see output from gpg –list-keys<\/em>).<\/p>\n Now we can sign our tags using<\/p>\n We replace -a with -s, this is now a signed, annotated tag.<\/p>\n We’ll probably want to verify our tag, and we do this using<\/p>\n If you have the public key installed you’ll see information about the key, if not then you’ll get a verification error.<\/p>\n","protected":false},"excerpt":{"rendered":" Creating tags from the command line… Tags allows us to store a pointer to the repository at a point in time, these are often used for “tagging” a release, but can be used for other purposes. Note: I will use the tag name v1.0.2 here, obviously this should be replaced with the tagname you’ve used\/assigned. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[206],"tags":[],"class_list":["post-8140","post","type-post","status-publish","format-standard","hentry","category-git-2"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/8140","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/comments?post=8140"}],"version-history":[{"count":4,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/8140\/revisions"}],"predecessor-version":[{"id":8144,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/8140\/revisions\/8144"}],"wp:attachment":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/media?parent=8140"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/categories?post=8140"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/tags?post=8140"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\r\ngit tag\r\n<\/pre>\n
\r\ngit tag -a v1.0.2 -m "Version 1.0.2"\r\n<\/pre>\n
\r\ngit tag v1.0.2\r\n<\/pre>\n
\r\ngit tag v1.0.2 6a0b83\r\n<\/pre>\n
\r\ngit push origin v1.0.2\r\n<\/pre>\n
\r\ngit push origin --tags\r\n<\/pre>\n
\r\ngit show v1.0.2\r\n<\/pre>\n
\r\ngit tag -d v1.0.2\r\n<\/pre>\n
\r\ngit push origin :refs\/tags\/v1.0.2\r\n<\/pre>\n
\r\ngit push origin --delete v1.0.2\r\n<\/pre>\n
\r\ngit checkout v1.0.2\r\n<\/pre>\n
\r\ngit checkout -b v1.0.2-branch v1.0.2\r\n<\/pre>\n
\r\ngpg --list-keys\r\n<\/pre>\n
\r\ngpg --gen-key\r\n<\/pre>\n
\r\ngit config --global user.signingkey 123456789\r\n<\/pre>\n
\r\ngit tag -s v1.0.2 -m "Version 1.0.2"\r\n<\/pre>\n
\r\ngit tag -v v1.0.2\r\n<\/pre>\n