Semantic versioning with tags in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is semantic versioning in Git tags?

Semantic versioning is a way to name Git tags using a format like MAJOR.MINOR.PATCH. It helps track changes clearly: MAJOR for big changes, MINOR for new features, PATCH for fixes.

beginner

What does the tag v2.1.0 tell you about the project?

The tag v2.1.0 means the project is on major version 2, minor version 1, and patch 0. It shows new features were added since version 2.0.0, but no bug fixes yet.

beginner

How do you create a lightweight Git tag named v1.0.0?

Use the command: git tag v1.0.0. This creates a simple tag pointing to the current commit.

intermediate

How do annotated tags differ from lightweight tags in Git?

Annotated tags store extra info like tagger name, date, and message. Lightweight tags are just simple pointers to commits without extra data.

beginner

What command lists all tags in a Git repository?

Use git tag to list all tags. You can see all semantic version tags this way.

What does the PATCH number in semantic versioning represent?

A Bug fixes and small improvements

B New features added

C Big changes that break compatibility

D Changes to documentation only

PATCH is for bug fixes and small improvements that do not change features or break compatibility.

Which command creates an annotated tag named v1.2.3?

A git tag v1.2.3

B git create tag v1.2.3

C git tag -a v1.2.3 -m "Release 1.2.3"

D git tag --list v1.2.3

The -a option creates an annotated tag with a message.

What does the tag v3.0.0 usually indicate?

A Patch update

B Major update with possible breaking changes

C Minor feature update

D Pre-release version

The major version change (3) means big updates that might break compatibility.

How do you see all tags in your Git repository?

A git show tags

B git list tags

C git tags --all

D git tag

The command 'git tag' lists all tags.

Why use semantic versioning tags in Git?

A To track changes clearly and help users know update types

B To confuse users

C To slow down development

D To avoid using branches

Semantic versioning helps everyone understand the type of changes in each release.

Explain semantic versioning and how it helps in managing Git tags.

Think about how you tell a friend if a new app update is big or small.

Describe the difference between lightweight and annotated Git tags and when to use each.

Imagine writing a quick note versus a detailed letter.