Tagging specific commits in Git - Mini Project: Build & Apply

Tagging Specific Commits in Git

📖 Scenario: You are working on a project using Git for version control. You want to mark important points in your project's history by tagging specific commits. This helps you easily find those commits later, like marking chapters in a book.

🎯 Goal: Learn how to create a Git repository, make commits, add tags to specific commits, and list those tags.

📋 What You'll Learn

Create a Git repository

Make at least two commits

Tag a specific commit with a meaningful name

List all tags to verify

💡 Why This Matters

🌍 Real World

Tagging commits helps mark important versions like releases or milestones in software projects.

💼 Career

Knowing how to tag commits is essential for software developers and DevOps engineers to manage project versions and releases.

1

Initialize Git repository and create first commit

Initialize a new Git repository in the current folder using git init. Then create a file named file.txt with the text Hello World. Add this file to Git and commit it with the message Initial commit using git add file.txt and git commit -m "Initial commit".

Git

# Initialize Git repository and create first commit
# Your code here

Hint

Use git init to start the repository. Use echo to create the file. Then add and commit.

2

Create a second commit

Create a second commit by appending the text More content to file.txt. Then add and commit the changes with the message Second commit using git add file.txt and git commit -m "Second commit".

Git

git init

echo "Hello World" > file.txt
git add file.txt
git commit -m "Initial commit"
# Append text to file.txt and create second commit
# Your code here

Hint

Use >> to append text to the file. Then add and commit again.

3

Tag the first commit

Create a tag named v1.0 on the first commit. Use git tag v1.0 <commit-hash> where <commit-hash> is the hash of the first commit. Find the first commit hash using git log --reverse --format=%H and use it in the tag command.

Git

git init

echo "Hello World" > file.txt
git add file.txt
git commit -m "Initial commit"

echo "More content" >> file.txt
git add file.txt
git commit -m "Second commit"
# Tag the first commit with 'v1.0'
# Your code here

Hint

Use git log --reverse --format=%H to get commits from oldest to newest. Use head -n 1 to get the first commit hash.

4

List all tags to verify

List all tags in the repository using git tag to verify that the tag v1.0 exists.

Git

git init

echo "Hello World" > file.txt
git add file.txt
git commit -m "Initial commit"

echo "More content" >> file.txt
git add file.txt
git commit -m "Second commit"

first_commit_hash=$(git log --reverse --format=%H | head -n 1)
git tag v1.0 $first_commit_hash
# List all tags below
# Your code here

Hint

Use git tag to see all tags.

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