Git Notes
HubBenefits of Git and GitHub - Why They MatterGit vs GitHubVersion Control SystemWhat Is GitWhat Is GitHubConfigure Git - User Identity and SettingsCreate GitHub Account - Sign Up GuideFirst Git Repository - Getting StartedInstall Git on Linux - Complete Setup GuideInstall Git on macOS - Installation GuideInstall Git on Windows - Step-by-Step GuideGit Add - Stage ChangesGit Clone - Copy Remote Repositories LocallyGit Commit - Save ChangesGit Diff - Compare Changes in Your RepositoryGit Ignore - Exclude Files from Version ControlGit Init - Initialize RepositoryGit Log - View Commit HistoryGit Status - Check Repository StateGit Fetch - Download Remote Changes Without MergingGit Pull - Fetch and Merge Remote ChangesGit Push - Upload Local Commits to Remote RepositoryGit Remote - Manage Remote Repository ConnectionsLocal Repository - Understanding Your Git Working EnvironmentRemote Repository - Collaborate Through Shared RepositoriesSync Local and Remote - Keep Repositories in HarmonyAmend Commit - Fix Last CommitDelete Branch - Clean Up BranchesGit Reset - Move HEAD and Undo CommitsGit Restore - Discard ChangesGit Revert - Safely Undo ChangesRecover Lost Commits - Reflog GuideFork RepositoryGitHub PagesGitHub Profile SetupGitHub RepositoriesGitHub Stars and WatchersRepository SettingsCode ReviewsGit CloneGit FetchGit PullGit PushGitHub IssuesLabels and MilestonesOpen Source ContributionsGitHub Project BoardsPull Requests - Propose and Review Code ChangesTeam Collaboration with Git and GitHubAutomated Testing with GitHub ActionsCI/CD with GitHub ActionsDeployment Automation with GitHub ActionsIntroduction to GitHub ActionsGitHub Actions RunnersGitHub Actions WorkflowsEnterprise Git Workflows - Scale Git for Large OrganizationsFeature Branch Workflow - Isolate Development WorkGitFlow Workflow - Structured Release ManagementMonorepo Workflow - Manage Multiple Projects in One RepositoryTrunk-Based Development - Ship Code Fast and SafelyDeployment WorkflowsGitHub Pages DeploymentNetlify Deployment from GitHubRender Deployment from GitHubVercel Deployment from GitHubBranch Protection Rules - Secure Your Git BranchesPersonal Access Tokens - Authenticate with GitHubRepository Security Best PracticesSecret Scanning - Detect Leaked Credentials in CodeSigned Commits - Verify Commit Authenticity with GPGSSH Keys - Secure Git Authentication Without PasswordsGit Bisect - Find Bugs with Binary SearchGit Cherry-Pick - Apply Specific Commits to Any BranchGit Hooks - Automate Workflows with Git EventsGit Internals - Understanding How Git Works Under the HoodGit Stash - Temporarily Save Uncommitted ChangesGit Submodules - Manage External Dependencies as Git ReposGit Tag - Mark Important Points in HistoryGit Worktrees - Work on Multiple Branches SimultaneouslyCollaborative Web App ProjectComplete Team Workflow ProjectGitHub Actions Project - Build a CI/CD PipelineOpen Source Project Contribution - Guided ExercisePortfolio Project with Git - Showcase Your SkillsGit Command CheatsheetGit Interview Questions - Comprehensive Preparation GuideGitHub Interview QuestionsScenario-Based Git Interview QuestionsGit Troubleshooting GuideGit Best Practices - Professional Development HabitsCommon Git Errors and Fixes - Quick SolutionsGit Command Reference - Complete Command GuideLearning Resources - Continue Your Git & GitHub EducationBranch Strategies - Choosing the Right Git Branching ModelCreate Branch in Git - Start New Development LinesFast-Forward Merge in Git - Clean Linear HistoryGit BranchGit CheckoutGit MergeGit RebaseMerge Branches in Git - Combine Development WorkMerge Conflicts - Resolve Git Conflicts Like a ProSwitch Branch in Git - Navigate Between Branches
Learn how to create, list, and manage Git tags for releases and milestones. Understand lightweight vs annotated tags, semantic versioning, and tag workflows.
Git tags mark specific commits as important milestones — typically used for release versions (v1.0.0, v2.1.3). Unlike branches, tags do not move; they permanently point to a specific commit.
Types of Tags
Lightweight Tags
Simple pointers to a commit (like a branch that does not move):
bash example
git tag v1.0.0Annotated Tags (Recommended)
Full objects with tagger name, date, message, and optional GPG signature:
bash example
git tag -a v1.0.0 -m "Release version 1.0.0"Output
# No output on success
bash example
# View annotated tag details
git show v1.0.0Output
tag v1.0.0
Tagger: Jane Doe <jane@example.com>
Date: Mon Jan 15 10:00:00 2024 -0500
Release version 1.0.0
commit a1b2c3d4e5f6789012345678901234567890abcd
Author: Jane Doe <jane@example.com>
Date: Mon Jan 15 09:45:00 2024 -0500
Final preparations for v1.0.0 releaseCreating Tags
Tag Current Commit
bash example
# Annotated (recommended)
git tag -a v2.0.0 -m "Major release with new UI"
# Lightweight
git tag v2.0.0-betaTag a Past Commit
bash example
git tag -a v1.5.0 -m "Patch release" abc1234Tag with Semantic Versioning
| MAJOR: Breaking changes (v1.0.0 | v2.0.0) |
| MINOR: New features, backwards compatible (v1.0.0 | v1.1.0) |
| PATCH: Bug fixes, backwards compatible (v1.0.0 | v1.0.1) |
| Pre-release | v2.0.0-beta.1, v2.0.0-rc.1 |
| Build metadata | v1.0.0+build.123 |
Listing Tags
bash example
# List all tags
git tagOutput
v1.0.0 v1.1.0 v1.2.0 v2.0.0 v2.0.1
bash example
# Filter tags by pattern
git tag -l "v2.*"Output
v2.0.0 v2.0.1
bash example
# Sort by version number
git tag --sort=version:refnamebash example
# Show tags with messages
git tag -nOutput
v1.0.0 Initial stable release v1.1.0 Add user authentication v2.0.0 Major release with new UI
Pushing Tags
Tags are NOT pushed by default with git push:
bash example
# Push a specific tag
git push origin v1.0.0
# Push ALL tags
git push origin --tags
# Push only annotated tags (not lightweight)
git push origin --follow-tagsOutput
Enumerating objects: 1, done. Counting objects: 100% (1/1), done. Writing objects: 100% (1/1), 175 bytes | 175.00 KiB/s, done. Total 1 (delta 0), reused 0 (delta 0) To https://github.com/user/repo.git * [new tag] v1.0.0 -> v1.0.0
Deleting Tags
bash example
# Delete local tag
git tag -d v1.0.0-betaOutput
Deleted tag 'v1.0.0-beta' (was a1b2c3d)
bash example
# Delete remote tag
git push origin --delete v1.0.0-beta
# or
git push origin :refs/tags/v1.0.0-betaChecking Out Tags
bash example
# View code at a tag (detached HEAD)
git checkout v1.0.0Output
Note: switching to 'v1.0.0'. You are in 'detached HEAD' state... HEAD is now at a1b2c3d Final preparations for v1.0.0 release
bash example
# Create a branch from a tag (to make changes)
git checkout -b hotfix/v1.0.1 v1.0.0Release Workflow with Tags
bash example
# 1. Finish all work for the release
git checkout main
git pull origin main
# 2. Create annotated tag
git tag -a v1.2.0 -m "Release v1.2.0: Add payment integration"
# 3. Push the tag
git push origin v1.2.0
# 4. GitHub automatically creates a release (if configured)
# Or create manually on GitHub Releases pageComparing Tags
bash example
# See commits between two tags
git log v1.0.0..v2.0.0 --onelineOutput
a1b2c3d Add new dashboard b2c3d4e Refactor authentication c3d4e5f Fix database connection d4e5f6g Update dependencies
bash example
# See file changes between tags
git diff v1.0.0 v2.0.0 --statInterview Questions
- What is the difference between a lightweight and annotated tag?
A lightweight tag is just a pointer to a commit (like a branch that does not move). An annotated tag is a full Git object with tagger info, date, message, and optional GPG signature. Annotated tags are recommended for releases.
- Why are tags not pushed by default?
Tags are considered local metadata by Git. This prevents accidentally publishing tags. You must explicitly push with git push origin <tag> or git push --tags.
- How do you create a tag for a past commit?
Use git tag -a v1.0.0 -m "message" <commit-hash>. This creates an annotated tag pointing to the specified historical commit.
- What happens when you checkout a tag?
You enter a detached HEAD state because tags point to commits, not branches. If you need to make changes, create a branch from the tag with git checkout -b branch-name tag-name.
- How is semantic versioning used with Git tags?
Tags follow the format vMAJOR.MINOR.PATCH. MAJOR for breaking changes, MINOR for backward-compatible features, PATCH for backward-compatible fixes. Pre-release versions use suffixes like -beta.1 or -rc.1.
Exam Focus
Revise definitions, diagrams, examples, and short-answer points for Git Tag - Mark Important Points in History.
Interview Use
Prepare one clear explanation, one practical example, and one common mistake for this Git & GitHub topic.
Search Terms
git-github, git & github, git, github, advanced, tag, git tag - mark important points in history
Related Git & GitHub Topics
Continue learning this concept
Advanced GitGit Bisect - Find Bugs with Binary SearchLearn how to use git bisect to efficiently find the commit that introduced a bug using binary search. Master automated bisect with scripts and practical debugging workflows.Advanced GitGit Cherry-Pick - Apply Specific Commits to Any BranchLearn how to use git cherry-pick to apply individual commits from one branch to another. Master cherry-pick options, conflict resolution, and best practices.Advanced GitGit Hooks - Automate Workflows with Git EventsLearn to use Git hooks for automating code quality checks, commit message validation, pre-push testing, and deployment triggers. Covers client-side and server-side hooks.Advanced GitGit Internals - Understanding How Git Works Under the HoodDeep dive into Git internals including objects (blobs, trees, commits), the SHA-1 hash system, packfiles, refs, and how Git stores data as a content-addressable filesystem.Advanced GitGit Stash - Temporarily Save Uncommitted ChangesMaster git stash to save work-in-progress changes without committing. Learn stash operations, named stashes, partial stashing, and workflow patterns.Advanced GitGit Submodules - Manage External Dependencies as Git ReposLearn how to use Git submodules to include external repositories within your project. Cover adding, updating, cloning with submodules, and alternatives.