lab 13 Tagging versions
Goals
- Learn how to tag commits with names for future reference
Let’s call the current version of the hello program version 1 (v1).
Tagging version 1 01
Execute:
git tag v1
Now you can refer to the current version of the program as v1.
Tagging Previous Versions 02
Let’s tag the version immediately prior to the current version v1-beta. First we need to checkout the previous version. Rather than lookup up the hash, we will use the ^
notation to indicate “the parent of v1”.
If the v1
^ notation gives you any trouble, you can also try v1~1
, which will reference the same version. This notation means “the first ancestor of v1”.
Execute:
git checkout v1^ cat hello.rb
Output:
$ git checkout v1^ Note: checking out 'v1^'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at 582495a... Added a default value $ cat hello.rb name = ARGV.first || "World" puts "Hello, #{name}!"
See, this is the version with the default value before we added the comment. Let’s make this v1-beta.
Execute:
git tag v1-beta
Checking Out by Tag Name 03
Now try going back and forth between the two tagged versions.
Execute:
git checkout v1 git checkout v1-beta
Output:
$ git checkout v1 Previous HEAD position was 582495a... Added a default value HEAD is now at 1f7ec5e... Added a comment $ git checkout v1-beta Previous HEAD position was 1f7ec5e... Added a comment HEAD is now at 582495a... Added a default value
Viewing Tags using the tag
command 04
You can see what tags are available using the git tag
command.
Execute:
git tag
Output:
$ git tag v1 v1-beta
Viewing Tags in the Logs 05
You can also check for tags in the log.
Execute:
git hist master --all
Output:
$ git hist master --all * 1f7ec5e 2013-04-13 | Added a comment (v1, master) [Jim Weirich] * 582495a 2013-04-13 | Added a default value (HEAD, v1-beta) [Jim Weirich] * 323e28d 2013-04-13 | Using ARGV [Jim Weirich] * 9416416 2013-04-13 | First Commit [Jim Weirich]
You can see both tags (v1
and v1-beta
) listed in the log output, along with the branch name (master
). Also HEAD
shows you the currently checked out commit (which is v1-beta
at the moment).