Complete Git Guide: Understand and Master Git and GitHub - Lightweight Versus Annotated Tags

The video tutorial explains the process of updating software versions in Git after merging branches, highlighting the differences between minor and patch updates. It delves into the two types of Git tags: lightweight and annotated, explaining their creation, storage, and usage. Annotated tags are recommended due to their ability to store additional metadata like author and date. The tutorial also covers the importance of unique tag names and explores how tags are stored in the Git repository.

What is the primary reason for updating only the patch version after merging a branch?

• A small bug was fixed.

• A major feature was added.

• The user interface was redesigned.

• The software was completely rewritten.

Which command is used to create a lightweight tag in Git?

• git merge

• git tag

• git branch

• git commit

What is a key characteristic of lightweight tags?

• They are stored in the Git objects folder.

• They can be moved like branches.

• They are static pointers to specific commits.

• They store the author's name and date.

What additional information can annotated tags store compared to lightweight tags?

• File changes

• Commit history

• Branch names

• Tag message, author, and date

Where are annotated tags stored in a Git repository?

• In both Git ref tags and Git objects folders

• In the Git branches folder

• In the Git objects folder only

• In the Git ref tags folder only