Tagging specific commits in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this git tag command?

You run the command git tag -a v1.0 9fceb02 -m "Release version 1.0". What does this command do?

Git

git tag -a v1.0 9fceb02 -m "Release version 1.0"

A Creates a lightweight tag named 'v1.0' on the latest commit with the message 'Release version 1.0'.

B Creates an annotated tag named 'v1.0' on commit '9fceb02' with the message 'Release version 1.0'.

C Deletes the tag 'v1.0' from commit '9fceb02'.

D Lists all tags that contain the message 'Release version 1.0'.

💡 Hint

The '-a' option creates an annotated tag, and '-m' adds a message.

The command creates an annotated tag named 'v1.0' on the specific commit '9fceb02'. The '-a' flag means annotated tag, and '-m' adds the tag message.

🧠 Conceptual

intermediate

Which git command shows the commit a tag points to?

You want to see the commit hash that a tag named 'v2.0' points to. Which command will show this?

A git checkout v2.0

B git log v2.0 --oneline

C git show v2.0

D git tag -l v2.0

💡 Hint

One command shows tag details including the commit.

git show v2.0 displays the commit and tag details for the tag 'v2.0'.

❓ Troubleshoot

advanced

Why does this tag command fail?

You run git tag -a v3.0 abc1234 -m "Version 3.0" but get an error: fatal: Not a valid object name abc1234. What is the likely cause?

Git

git tag -a v3.0 abc1234 -m "Version 3.0"

A The commit hash 'abc1234' does not exist in the repository.

B The tag name 'v3.0' is already used for another tag.

C The message flag '-m' cannot be used with '-a'.

D You need to add '--force' to overwrite existing tags.

💡 Hint

Check if the commit hash exists in your repo.

The error means the commit hash 'abc1234' is not found. You must use a valid commit hash to tag.

🔀 Workflow

advanced

How to push a specific tag to remote?

You created a tag 'release-1.1' locally. Which command pushes only this tag to the remote repository?

A git push --all origin

B git push origin --tags

C git push origin HEAD

D git push origin release-1.1

💡 Hint

Pushing all tags uses a different flag.

git push origin release-1.1 pushes only the specified tag to the remote.

✅ Best Practice

expert

What is the best practice for tagging a release commit?

You want to tag a release commit so that it includes metadata like author, date, and a message. Which tag type should you use?

A Annotated tag

B Signed tag without message

C Lightweight tag

D Temporary tag

💡 Hint

One tag type stores extra information and is recommended for releases.

Annotated tags store metadata such as author, date, and a message. They are best for marking releases.