Semantic versioning with tags in Git - Step-by-Step Execution

Process Flow - Semantic versioning with tags

Start: Code changes ready

↓

Decide version bump: Major, Minor, Patch

↓

Create tag: vMAJOR.MINOR.PATCH

↓

Push tag to remote

↓

Tag used to mark release version

Semantic versioning tags mark releases with major, minor, and patch numbers to track changes clearly.

Execution Sample

Git

git tag v1.2.3

git push origin v1.2.3

Create a semantic version tag v1.2.3 and push it to the remote repository.

Process Table

Step	Command	Action	Result
1	git tag v1.2.3	Create a tag named v1.2.3	Tag v1.2.3 created locally
2	git push origin v1.2.3	Push the tag to remote repository	Tag v1.2.3 pushed to remote
3	git tag	List all tags	v1.2.3 shown in tag list
4	git show v1.2.3	Show commit details for tag	Commit info for tagged version displayed

💡 Tag v1.2.3 created and pushed successfully, marking the release version.

Status Tracker

Variable	Start	After Step 1	After Step 2	Final
Tags	none	v1.2.3 (local)	v1.2.3 (local + remote)	v1.2.3 (local + remote)

Key Moments - 3 Insights

Why do we use tags like v1.2.3 instead of just commit hashes?

Tags like v1.2.3 give a clear, human-friendly version number marking releases, unlike commit hashes which are long and not descriptive. See execution_table step 1 and 3.

What happens if I create a tag but don't push it?

The tag exists only on your local machine and others can't see it. Step 2 in execution_table shows pushing makes it available remotely.

How do I know which commit a tag points to?

Using 'git show <tag>' displays the commit details the tag references, as shown in step 4 of execution_table.

Visual Quiz - 3 Questions

Look at the execution table, what is the result after running 'git tag v1.2.3'?

A Tag deleted

B Tag pushed to remote

C Tag v1.2.3 created locally

D No tag created

💡 Hint

Check the 'Result' column in step 1 of the execution_table.

At which step is the tag pushed to the remote repository?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the 'Command' and 'Action' columns in the execution_table.

If you skip step 2, what will the 'Tags' variable show after step 3?

A v1.2.3 (local + remote)

B v1.2.3 (local only)

C No tags

D v1.2.3 deleted

💡 Hint

Refer to variable_tracker and the explanation in key_moments about pushing tags.

Concept Snapshot

Semantic versioning tags use format vMAJOR.MINOR.PATCH
Create tags with 'git tag vX.Y.Z'
Push tags with 'git push origin vX.Y.Z'
Tags mark release points clearly
Tags help track versions beyond commit hashes

Full Transcript

Semantic versioning with tags means marking your code releases with clear version numbers like v1.2.3. You create a tag locally using 'git tag v1.2.3' which points to a specific commit. Then you push this tag to the remote repository with 'git push origin v1.2.3' so others can see it. Tags help identify release versions easily instead of using long commit hashes. You can list tags with 'git tag' and see details with 'git show v1.2.3'. This process helps teams track and manage software versions clearly.