Creating tags in Git - Practice Exercises

Challenge - 5 Problems

💻 Command Output

intermediate

Output of creating an annotated tag

What is the output of running the following command in a Git repository?

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

Git

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

A Creates an annotated tag named v1.0 with the message 'Release version 1.0' and no output is shown

B Creates a lightweight tag named v1.0 and outputs 'Tag v1.0 created'

C Creates an annotated tag named v1.0 and outputs 'Annotated tag v1.0 created with message Release version 1.0'

D Throws an error because the -m option is invalid with -a

💡 Hint

Annotated tags store extra information like messages but do not print output by default.

The command creates an annotated tag with the given message. Git does not print any output when creating tags successfully.

🧠 Conceptual

intermediate

Difference between lightweight and annotated tags

Which statement correctly describes the difference between lightweight and annotated tags in Git?

A Lightweight tags are simple pointers to commits; annotated tags store extra metadata like author, date, and message

B Annotated tags are pointers to branches; lightweight tags store commit messages

C Lightweight tags can only be created locally; annotated tags are automatically pushed to remote

D Annotated tags are temporary and deleted after checkout; lightweight tags are permanent

💡 Hint

Think about what extra information annotated tags hold compared to lightweight tags.

Lightweight tags are just names pointing to commits. Annotated tags include extra information like author, date, and a message.

🔀 Workflow

advanced

Correct sequence to create and push an annotated tag

What is the correct order of commands to create an annotated tag named v2.0 with message 'Second release' and push it to the remote repository?

A 4, 1, 3, 2

B 1, 4, 2, 3

C 1, 2, 4, 3

D 4, 1, 2, 3

💡 Hint

You must be on the correct branch before tagging, then push the tag, then update local info.

First checkout the branch to tag, then create the annotated tag, push it to remote, and finally fetch to update local references.

❓ Troubleshoot

advanced

Error when pushing tags to remote

You created a tag locally using git tag v3.0 but when you run git push, the tag does not appear on the remote. What is the reason?

A The tag name v3.0 is invalid and rejected by the remote

B Tags are not pushed by default with 'git push'; you must explicitly push tags

C You need to delete the tag locally and recreate it as annotated to push

D The remote repository does not support tags

💡 Hint

Think about how Git handles tags during push operations.

By default, 'git push' does not push tags. You must run 'git push origin --tags' or 'git push origin ' to push tags.

✅ Best Practice

expert

Recommended practice for tagging releases in a team

Which practice is best when multiple developers create tags for releases in a shared Git repository?

A Use only lightweight tags locally and convert them to annotated tags on the remote

B Each developer creates tags locally and never pushes them to avoid conflicts

C Agree on a naming convention and push tags to remote immediately after creation

D Avoid using tags and rely only on branch names for releases

💡 Hint

Think about coordination and clarity in a team environment.

Agreeing on naming conventions and pushing tags immediately helps keep the team synchronized and avoids confusion.