Tagging specific commits in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Git tag?

A Git tag is a label that points to a specific commit. It helps mark important points like releases or versions in the project history.

beginner

How do you create a lightweight tag on a specific commit?

Use the command git tag <tagname> <commit-hash>. This creates a simple tag pointing to that commit without extra information.

intermediate

What is the difference between lightweight and annotated tags in Git?

Lightweight tags are simple pointers to commits. Annotated tags store extra info like tagger name, date, and message, and are stored as full objects in Git.

intermediate

How do you create an annotated tag on a specific commit?

Use git tag -a <tagname> <commit-hash> -m "message". This adds a message and extra info to the tag.

beginner

How can you push a specific tag to a remote repository?

Use git push origin <tagname> to send the tag to the remote repository so others can see it.

Which command creates a lightweight tag on commit abc123?

A git commit -m "tag v1.0"

B git tag -a v1.0 abc123 -m "version 1.0"

C git tag v1.0 abc123

D git push origin v1.0

Option C creates a lightweight tag named v1.0 on commit abc123.

What extra information does an annotated tag include?

A Commit hash only

B Branch name

C Remote URL

D Tagger name, date, and message

Annotated tags store tagger name, date, and a message along with the commit reference.

How do you push all tags to the remote repository?

A git push origin --tags

B git push origin master

C git push origin HEAD

D git tag push

The command 'git push origin --tags' pushes all local tags to the remote.

Which command creates an annotated tag with a message?

A git tag v1.0

B git tag -a v1.0 -m "release"

C git tag -d v1.0

D git push origin v1.0

Option B creates an annotated tag with the message 'release'.

If you want to tag a commit but don’t remember its hash, what can you do?

A Use git log to find the commit hash

B Use git push

C Use git branch

D Use git clone

You can use 'git log' to see commit history and find the commit hash to tag.

Explain how to create and push an annotated tag on a specific commit in Git.

Think about tagging with extra info and sharing it with others.

Describe the difference between lightweight and annotated tags and when you might use each.

Consider the detail and purpose of the tag.

Practice

1. What is the main purpose of tagging a commit in Git?

easy

A. To delete a commit permanently

B. To label a specific commit for easy reference later

C. To merge two branches automatically

D. To create a new branch from the commit

Solution

1. Step 1: Understand what a tag does

   A tag in Git is a label that points to a specific commit, making it easy to find later.

2. Step 2: Compare options with tag purpose

   Deleting commits, merging branches, or creating branches are different Git actions unrelated to tagging.

3. Final Answer:

   To label a specific commit for easy reference later -> Option B

4. Quick Check:

   Tag = label commit [OK]

Hint: Tags mark commits for quick access later [OK]

Common Mistakes:

• Confusing tags with branches
• Thinking tags delete commits
• Assuming tags merge code

2. Which of the following commands correctly tags a commit with hash abc123 as v1.0?

easy

A. git tag -m v1.0 abc123

B. git tag abc123 v1.0

C. git tag v1.0 abc123

D. git commit tag v1.0 abc123

Solution

1. Step 1: Recall git tag syntax

   The correct syntax to tag a specific commit is git tag <tagname> <commit-hash>.

2. Step 2: Match syntax with options

   git tag v1.0 abc123 matches the correct order: tag name first, then commit hash. Others have wrong order or invalid flags.

3. Final Answer:

   git tag v1.0 abc123 -> Option C

4. Quick Check:

   git tag <tag> <commit> [OK]

Hint: Tag name comes before commit hash in command [OK]

Common Mistakes:

• Swapping tag name and commit hash
• Using git commit instead of git tag
• Adding wrong flags like -m without message

3. What will be the output of git show v2.0 if v2.0 is a tag pointing to commit def456?

medium

A. Shows details of the commit with hash def456

B. Lists all tags in the repository

C. Deletes the tag v2.0

D. Shows the commit history of the current branch

Solution

1. Step 1: Understand git show with a tag

   Running git show <tag> displays the commit details the tag points to.

2. Step 2: Match output with options

   Shows details of the commit with hash def456 correctly describes the output. Other options describe different commands or actions.

3. Final Answer:

   Shows details of the commit with hash def456 -> Option A

4. Quick Check:

   git show tag = commit details [OK]

Hint: git show tag shows tagged commit info [OK]

Common Mistakes:

• Thinking git show lists all tags
• Confusing git show with git tag commands
• Assuming git show deletes tags

4. You tried to tag a commit with git tag v1.1 abc789 but got an error saying "fatal: Not a valid object name abc789". What is the likely cause?

medium

A. The tag name v1.1 is already used

B. You forgot to push the tag to the remote

C. You need to add -m message to the tag command

D. The commit hash abc789 does not exist in the repository

Solution

1. Step 1: Analyze the error message

   "Not a valid object name" means Git cannot find the commit hash specified.

2. Step 2: Check other options

   Not pushing tags or tag name conflicts cause different errors. -m is optional for annotated tags.

3. Final Answer:

   The commit hash abc789 does not exist in the repository -> Option D

4. Quick Check:

   Invalid commit hash = error [OK]

Hint: Check commit hash exists before tagging [OK]

Common Mistakes:

• Assuming tag name conflict causes this error
• Thinking push is needed before tagging
• Forcing -m message without need

5. You want to tag the commit that is two commits behind the current HEAD with the tag release-2024. Which command should you use?

hard

A. git tag release-2024 HEAD~2

B. git tag release-2024 HEAD^2

C. git tag release-2024 HEAD~

D. git tag release-2024 HEAD-2

Solution

1. Step 1: Understand commit references

   In Git, HEAD~2 means two commits before HEAD. HEAD^2 means second parent of a merge commit, which is different.

2. Step 2: Match correct syntax for tagging

   git tag release-2024 HEAD~2 correctly tags the commit two behind HEAD. Options C and D are invalid or incorrect references.

3. Final Answer:

   git tag release-2024 HEAD~2 -> Option A

4. Quick Check:

   HEAD~2 = two commits behind [OK]

Hint: Use HEAD~N to tag N commits behind HEAD [OK]

Common Mistakes:

• Confusing HEAD~2 with HEAD^2
• Using invalid commit references like HEAD~ or HEAD-2
• Tagging wrong commit by mistake