Tagging specific commits in Git - Commands & Configuration

Introduction

Sometimes you want to mark a specific point in your project's history to remember a release or important change. Tagging lets you label a commit with a friendly name so you can find it easily later.

When you finish a version of your software and want to mark it as a release.

When you want to save a snapshot of your code before making big changes.

When you need to share a specific commit with your team as a reference point.

When you want to quickly switch back to a known good state in your project.

When you want to create a stable point for deployment or rollback.

Commands

Shows the last 5 commits with their short IDs and messages so you can pick the commit to tag.

Terminal

git log --oneline -5

Expected Output

a1b2c3d Fix login bug

f4e5d6c Add user profile page

9a8b7c6 Update README

123abcd Initial commit

789ef01 Setup project structure

→

--oneline - Shows each commit in one line for easy reading

→

-5 - Limits output to last 5 commits

Creates a lightweight tag named 'v1.0' on the commit with ID 'a1b2c3d' to mark it as version 1.0.

Terminal

git tag v1.0 a1b2c3d

Expected Output

No output (command runs silently)

Lists all tags in the repository to confirm the new tag was created.

Terminal

git tag

Expected Output

v1.0

Shows details about the commit that the tag 'v1.0' points to, including the commit message and changes.

Terminal

git show v1.0

Expected Output

commit a1b2c3d

Author: Jane Doe <[e-mail]>

Date:   Tue Apr 23 10:00:00 2024 +0000



    Fix login bug



diff --git a/login.py b/login.py

index e69de29..d95f3ad 100644

--- a/login.py

+++ b/login.py

@@ -1 +1,2 @@

+Fixed authentication error handling

Key Concept

If you remember nothing else from this pattern, remember: tags are simple labels that point to specific commits to mark important points in your project history.

Common Mistakes

Trying to tag a commit ID that does not exist or is mistyped.

Git will not create the tag and may show an error because the commit ID is invalid.

Use 'git log' to find the correct commit ID before tagging.

Creating a tag without specifying the commit ID, expecting it to tag the latest commit.

Git tags the current HEAD by default, but if you want a specific commit, you must specify it explicitly.

Always specify the commit ID if you want to tag a commit other than the latest.

Not pushing tags to the remote repository after creating them locally.

Tags exist only locally until you push them, so others won't see them.

Use 'git push origin v1.0' to share the tag with others.

Summary

Use 'git log --oneline' to find the commit ID you want to tag.

Create a tag with 'git tag <tagname> <commitID>' to mark that commit.

Verify tags with 'git tag' and inspect with 'git show <tagname>'.

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