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 branches in Git for feature development, bug fixes, and experimentation. Understand branch creation from different starting points.
Creating branches is one of Git's most powerful features. Branches let you work on features, fixes, or experiments in isolation without affecting the main codebase.
Understanding Branches
A branch in Git is simply a lightweight pointer to a specific commit. When you create a branch, Git creates a new pointer — it does not copy any files.
Before creating branch
main → [C1] ← [C2] ← [C3] (HEAD)
After creating feature branch
main → [C1] ← [C2] ← [C3]
↑
feature ──────────────────────┘ (HEAD)
Creating Branches
Method 1: git branch (Create Only)
This creates the branch but does not switch to it:
bash example
git branch feature-loginOutput
(no output - branch created silently)
You remain on your current branch. To switch:
bash example
git checkout feature-login
# or
git switch feature-loginMethod 2: git checkout -b (Create and Switch)
The most common approach — creates and switches in one command:
bash example
git checkout -b feature-loginOutput
Switched to a new branch 'feature-login'
Method 3: git switch -c (Modern Approach)
The newer, more intuitive command:
bash example
git switch -c feature-loginOutput
Switched to a new branch 'feature-login'
Creating Branches from Different Points
From Current Branch (Default)
bash example
# Creates branch at current HEAD
git checkout -b new-featureFrom a Specific Branch
bash example
# Create branch from develop, not from current branch
git checkout -b feature-api developFrom a Specific Commit
bash example
# Create branch from a past commit
git checkout -b hotfix-v1 abc1234Output
Switched to a new branch 'hotfix-v1'
From a Tag
bash example
# Create branch from a release tag
git checkout -b hotfix-release v2.0.0From a Remote Branch
bash example
# Create local branch tracking a remote branch
git checkout -b feature-x origin/feature-x
# Shorter form (auto-tracks if remote branch exists)
git checkout feature-xOutput
Branch 'feature-x' set up to track remote branch 'feature-x' from 'origin'. Switched to a new branch 'feature-x'
Step-by-Step Tutorial
Setting Up a Feature Branch Workflow
bash example
# Start on main branch with latest code
git checkout main
git pull origin main
# Create your feature branch
git checkout -b feature/user-dashboard
# Verify you are on the new branch
git branchOutput
main * feature/user-dashboard
bash example
# Start working on your feature
echo "Dashboard component" > dashboard.js
git add dashboard.js
git commit -m "Add initial dashboard component"
# Continue working...
echo "Dashboard styles" > dashboard.css
git add dashboard.css
git commit -m "Add dashboard styles"
# Check your branch history
git log --onelineOutput
b3c4d5e (HEAD -> feature/user-dashboard) Add dashboard styles a1b2c3d Add initial dashboard component f7e8d9c (origin/main, main) Initial commit
Listing Branches
bash example
# List local branches
git branchOutput
develop main * feature/user-dashboard feature/api-integration
bash example
# List remote branches
git branch -rOutput
origin/main origin/develop origin/feature/notifications
bash example
# List all branches (local + remote)
git branch -aOutput
develop main * feature/user-dashboard remotes/origin/main remotes/origin/develop remotes/origin/feature/notifications
bash example
# List branches with last commit info
git branch -vOutput
develop a1b2c3d Add API endpoint main f7e8d9c Initial commit * feature/user-dashboard b3c4d5e Add dashboard styles
Branch Creation Best Practices
Always Start from an Updated Base
bash example
# Update main before branching
git checkout main
git pull origin main
git checkout -b feature/new-featureUse Descriptive Names
bash example
# Good branch names
git checkout -b feature/JIRA-123-user-authentication
git checkout -b bugfix/fix-login-redirect
git checkout -b hotfix/patch-xss-vulnerability
# Bad branch names
git checkout -b my-branch
git checkout -b test
git checkout -b fixKeep Branches Focused
Each branch should represent one logical change:
bash example
# Good: One feature per branch
git checkout -b feature/add-search
git checkout -b feature/add-filters
# Bad: Multiple unrelated changes in one branch
git checkout -b feature/search-and-filters-and-refactorCommon Errors and Solutions
Branch Already Exists
bash example
git checkout -b feature-loginOutput
fatal: a branch named 'feature-login' already exists
Solution: Use a different name or switch to the existing branch:
bash example
git checkout feature-login # Switch to existing
# or
git checkout -b feature-login-v2 # Create with new nameUncommitted Changes Block Branch Switch
bash example
git checkout mainOutput
error: Your local changes to the following files would be overwritten by checkout:
app.js
Please commit your changes or stash them before you switch branches.Solution: Commit, stash, or discard changes:
bash example
# Option 1: Commit changes
git add . && git commit -m "WIP: save progress"
# Option 2: Stash changes
git stash
git checkout main
git checkout -b new-branch
git stash pop
# Option 3: Discard changes (careful!)
git checkout -- .Interview Questions
- What is the difference between
git branch featureandgit checkout -b feature?
git branch feature creates the branch but keeps you on the current branch. git checkout -b feature creates the branch and immediately switches to it.
- How do you create a branch from a specific commit?
Use git checkout -b branch-name commit-hash. This creates a new branch pointing to that specific commit in history.
- What happens internally when you create a branch?
Git creates a new pointer (a 41-byte file containing the commit SHA) in .git/refs/heads/. No files are copied — branches are extremely lightweight.
- How do you create a local branch that tracks a remote branch?
Use git checkout -b local-name origin/remote-name or simply git checkout remote-name if a matching remote branch exists — Git auto-creates a tracking branch.
- Should you create a branch from main or develop?
It depends on your branching strategy. In GitHub Flow, branch from main. In GitFlow, feature branches come from develop, while hotfixes come from main.
Exam Focus
Revise definitions, diagrams, examples, and short-answer points for Create Branch in Git - Start New Development Lines.
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, branching, and, merging, create
Related Git & GitHub Topics
Continue learning this concept
Branching And MergingBranch Strategies - Choosing the Right Git Branching ModelExplore popular Git branching strategies including GitFlow, GitHub Flow, and trunk-based development. Learn when to use each strategy for your team and project.Branching And MergingGit BranchBranching is one of the most powerful features in Git, and understanding how to work with branches effectively is what separates a beginner from a...Branching And MergingSwitch Branch in Git - Navigate Between BranchesLearn how to switch between branches using git checkout and git switch. Understand branch switching behavior, stashing changes, and handling uncommitted work.Branching And MergingFast-Forward Merge in Git - Clean Linear HistoryUnderstand fast-forward merges in Git, when they happen, how they differ from three-way merges, and how to control merge behavior with --no-ff and --ff-only flags.Branching And MergingGit CheckoutThe git checkout command is one of the most versatile commands in Git, which is both its strength and its source of confusion for newcomers. Historically,...Branching And MergingGit MergeMerging is the process of combining the work from two different branches into one. It is how features developed in isolation come together to form a...