Tagging specific commits in Git - Step-by-Step Execution

Process Flow - Tagging specific commits

Identify commit hash

↓

Run git tag command

↓

Tag created locally

↓

Optionally push tag to remote

↓

Tag visible in repo history

This flow shows how to create a tag on a specific commit by using its hash, then optionally push it to the remote repository.

Execution Sample

Git

git tag v1.0 9fceb02

git push origin v1.0

Create a tag named 'v1.0' on commit '9fceb02' and push it to the remote repository.

Process Table

Step	Command	Action	Result
1	git tag v1.0 9fceb02	Create tag 'v1.0' on commit 9fceb02	Tag 'v1.0' created locally
2	git tag	List all tags	Shows 'v1.0' among tags
3	git push origin v1.0	Push tag 'v1.0' to remote	Tag 'v1.0' pushed to remote
4	git ls-remote --tags origin	Verify remote tags	Remote shows 'refs/tags/v1.0'
5	-	End of process	Tagging complete and visible remotely

💡 Tag created locally and pushed to remote, process complete

Status Tracker

Variable	Start	After Step 1	After Step 3	Final
tags	none	v1.0 (local)	v1.0 (local + remote)	v1.0 (local + remote)

Key Moments - 3 Insights

Why do we need to specify the commit hash when tagging?

Because tags point to a specific commit, specifying the hash ensures the tag is placed exactly where intended, as shown in Step 1 of the execution_table.

What happens if we create a tag without pushing it?

The tag exists only on the local machine and won't be visible to others until pushed, as seen between Step 1 and Step 3.

How can we verify the tag exists on the remote repository?

By running 'git ls-remote --tags origin' as in Step 4, which lists all tags on the remote.

Visual Quiz - 3 Questions

Look at the execution table, what is the result immediately after running 'git tag v1.0 9fceb02'?

A No tag created

B Tag pushed to remote

C Tag 'v1.0' created locally

D Error: commit not found

💡 Hint

Check Step 1 in the execution_table under Result column

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

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look for 'git push origin v1.0' command in the execution_table

If you skip pushing the tag, what will the 'git ls-remote --tags origin' command show?

A No new tag listed

B The new tag listed

C An error message

D All tags except the new one

💡 Hint

Refer to Step 4 and the explanation in key_moments about pushing tags

Concept Snapshot

git tag <tagname> <commit-hash>  # Create tag on specific commit
Tags are local until pushed with:
git push origin <tagname>
Verify remote tags with:
git ls-remote --tags origin
Tags help mark important commits like releases.

Full Transcript

To tag a specific commit in git, first identify the commit hash you want to tag. Then run 'git tag <tagname> <commit-hash>' to create the tag locally. This tag points exactly to that commit. To share the tag with others, push it to the remote repository using 'git push origin <tagname>'. You can verify the tag exists remotely by running 'git ls-remote --tags origin'. Without pushing, the tag remains only on your local machine. This process helps mark important points in your project history, like releases or milestones.