Lightweight vs annotated tags in Git - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference between lightweight and annotated tags

Which statement correctly describes the difference between a lightweight tag and an annotated tag in Git?

A Both lightweight and annotated tags store the same metadata, but only annotated tags can be pushed to remote repositories.

B A lightweight tag is just a pointer to a commit, while an annotated tag stores extra metadata like the tagger's name, email, and date.

C An annotated tag is a simple pointer to a commit, while a lightweight tag stores metadata and a message.

D A lightweight tag stores the tagger's signature, but an annotated tag does not.

💡 Hint

Think about what extra information an annotated tag holds compared to a lightweight tag.

Lightweight tags are just simple references to commits without extra information. Annotated tags include metadata such as the tagger's name, email, date, and a message, making them more informative.

💻 Command Output

intermediate

Output of creating a lightweight tag

What is the output of the following command if executed successfully in a Git repository?

git tag v1.0

A No output is shown; the tag 'v1.0' is created as a lightweight tag.

B Error: tag name 'v1.0' is invalid.

C Created annotated tag 'v1.0' with message 'v1.0'.

D Warning: You must provide a message for the tag.

💡 Hint

Consider what happens when you create a tag without the -a option.

Running git tag v1.0 creates a lightweight tag silently without any output. Annotated tags require the -a option and a message.

💻 Command Output

advanced

Output of listing tags with details

What is the output of this command in a repository with annotated and lightweight tags?

git show v1.0

Assume v1.0 is an annotated tag with a message and v1.1 is a lightweight tag.

A Shows the tag message, tagger info, and commit details for 'v1.0'.

B Shows only the tag message without commit details.

C Shows an error because 'v1.0' is a lightweight tag.

D Shows only the commit details without tag metadata for 'v1.0'.

💡 Hint

Remember what information an annotated tag contains and what git show displays.

git show on an annotated tag displays the tag's metadata (message, tagger info) plus the commit details. Lightweight tags have no metadata, so only commit info is shown.

🔀 Workflow

advanced

Pushing annotated vs lightweight tags to remote

You want to push all your tags to the remote repository. Which command ensures both lightweight and annotated tags are pushed?

A git push origin --annotated-tags

B git push origin v1.0

C git push origin --all

D git push origin --tags

💡 Hint

Consider the command that pushes all tags regardless of type.

git push origin --tags pushes all tags, both lightweight and annotated, to the remote. --all pushes all branches, not tags.

❓ Troubleshoot

expert

Why does 'git push origin v1.0' fail for a lightweight tag?

You created a lightweight tag v1.0 locally but when you run git push origin v1.0, it fails with an error. What is the most likely reason?

A The tag <code>v1.0</code> does not exist locally.

B Lightweight tags cannot be pushed individually; only annotated tags can.

C You need to specify <code>refs/tags/v1.0</code> explicitly to push a lightweight tag.

D The remote repository does not accept pushing lightweight tags by default.

💡 Hint

Think about how Git references tags when pushing them individually.

When pushing a single tag, Git expects the full ref name refs/tags/v1.0. Without it, pushing a lightweight tag may fail. Annotated tags often push fine by name because of metadata handling.

Practice

1. What is the main difference between a lightweight tag and an annotated tag in Git?

easy

A. Annotated tags are simple pointers, while lightweight tags store author and date information.

B. Lightweight tags can only be created on branches, annotated tags only on commits.

C. Lightweight tags are simple pointers to commits, while annotated tags store extra information like author and message.

D. Annotated tags are temporary, lightweight tags are permanent.

Solution

1. Step 1: Understand lightweight tags

   Lightweight tags are just simple pointers to a commit without extra data.

2. Step 2: Understand annotated tags

   Annotated tags store additional info like author, date, and a message, making them more detailed.

3. Final Answer:

   Lightweight tags are simple pointers to commits, while annotated tags store extra information like author and message. -> Option C

4. Quick Check:

   Lightweight = pointer, Annotated = pointer + info [OK]

Hint: Remember: annotated tags hold extra info, lightweight just points [OK]

Common Mistakes:

• Confusing which tag stores extra info
• Thinking lightweight tags store author data
• Believing annotated tags are temporary

2. Which Git command correctly creates an annotated tag named v1.0 with a message?

easy

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

B. git tag --light v1.0 -m "Release version 1.0"

C. git tag -l v1.0 -m "Release version 1.0"

D. git tag v1.0 -m "Release version 1.0"

Solution

1. Step 1: Identify annotated tag creation syntax

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

2. Step 2: Check command correctness

   git tag -a v1.0 -m "Release version 1.0" uses git tag -a v1.0 -m "Release version 1.0", which is the correct syntax.

3. Final Answer:

   git tag -a v1.0 -m "Release version 1.0" -> Option A

4. Quick Check:

   Annotated tag = git tag -a [OK]

Hint: Use -a flag for annotated tags with messages [OK]

Common Mistakes:

• Using -l instead of -a for annotated tags
• Omitting -a flag when adding a message
• Using non-existent --light flag

3. Given the commands:

git tag v1.0
 git tag -a v2.0 -m "Second release"

What will git show v1.0 display?

medium

A. It will list all tags including v1.0 and v2.0.

B. It will show the tag message "Second release".

C. It will show an error because v1.0 is not annotated.

D. It will show the commit details without any tag message.

Solution

1. Step 1: Understand lightweight tag behavior with git show

   Lightweight tags are simple pointers, so git show shows commit info but no tag message.

2. Step 2: Compare with annotated tag output

   Annotated tags show extra info like messages; lightweight tags do not.

3. Final Answer:

   It will show the commit details without any tag message. -> Option D

4. Quick Check:

   git show lightweight tag = commit info only [OK]

Hint: git show on lightweight tags shows commit only, no message [OK]

Common Mistakes:

• Expecting a message on lightweight tags
• Thinking git show errors on lightweight tags
• Confusing git show output with git tag -l

4. You tried to create an annotated tag with git tag v1.1 -m "Update" but it created a lightweight tag instead. Why?

medium

A. Because -m cannot be used with annotated tags.

B. Because the -a flag was missing to specify an annotated tag.

C. Because the tag name v1.1 is invalid for annotated tags.

D. Because you need to push the tag first to make it annotated.

Solution

1. Step 1: Check command flags for annotated tags

   Annotated tags require the -a flag; without it, tags are lightweight.

2. Step 2: Analyze the given command

   The command lacks -a, so it created a lightweight tag despite the -m message.

3. Final Answer:

   Because the -a flag was missing to specify an annotated tag. -> Option B

4. Quick Check:

   Missing -a means lightweight tag [OK]

Hint: Always use -a for annotated tags, else lightweight is created [OK]

Common Mistakes:

• Assuming -m alone creates annotated tags
• Thinking tag name affects tag type
• Believing pushing changes tag type

5. You want to mark a release with a tag that includes author info, date, and a message, and you want this tag to be signed cryptographically. Which tag type should you use and how?

hard

A. Use a signed annotated tag with git tag -s v3.0 -m "Release 3.0".

B. Use an annotated tag with git tag -a v3.0 -m "Release 3.0".

C. Use a lightweight tag with git tag v3.0.

D. Use a signed lightweight tag with git tag -s v3.0.

Solution

1. Step 1: Identify tag type for extra info and signing

   Annotated tags store author, date, and message. Signed tags add cryptographic signature.

2. Step 2: Choose correct command for signed annotated tag

   The -s flag creates a signed annotated tag with message and author info.

3. Final Answer:

   Use a signed annotated tag with git tag -s v3.0 -m "Release 3.0". -> Option A

4. Quick Check:

   Signed annotated tag = git tag -s [OK]

Hint: Use -s for signed annotated tags with full info [OK]

Common Mistakes:

• Using lightweight tags for signing
• Using -a without -s for signing
• Thinking lightweight tags can be signed