Bird
Raised Fist0
Gitdevops~5 mins

What a branch is (pointer to a commit) in Git - Commands & Configuration

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction
When you work on a project, you often want to try new ideas without changing the main work. A branch in git is like a bookmark that points to a specific version of your project. It helps you keep track of different versions easily.
When you want to try a new feature without affecting the main project
When you need to fix a bug separately from ongoing work
When you want to share your work with others without mixing it with the main code
When you want to keep your main project stable while experimenting
When you want to organize your work into different tasks or ideas
Commands
This command lists all branches in your project and shows which one you are currently on.
Terminal
git branch
Expected OutputExpected
main * feature-1
This command creates a new branch called 'new-feature' pointing to the current commit. It does not switch to it yet.
Terminal
git branch new-feature
Expected OutputExpected
No output (command runs silently)
This command switches your working area to the 'new-feature' branch so you can start working there.
Terminal
git checkout new-feature
Expected OutputExpected
Switched to branch 'new-feature'
This command shows recent commits with branch names pointing to them, helping you see which commit each branch points to.
Terminal
git log --oneline --decorate
Expected OutputExpected
a1b2c3d (HEAD -> new-feature, main) Add new feature code 9f8e7d6 Fix typo in README
--oneline - Shows each commit in one line for easy reading
--decorate - Shows branch names and tags next to commits
Key Concept

If you remember nothing else, remember: a branch is just a name that points to a specific commit in your project history.

Common Mistakes
Creating a branch but not switching to it before making changes
Your changes will still go to the old branch, not the new one you created
After creating a branch, always switch to it using 'git checkout branch-name' before working
Deleting a branch without merging its changes
You lose the work done on that branch if it was not merged
Merge the branch into main or another branch before deleting it
Summary
Use 'git branch' to see all branches and which one is active.
Create a new branch with 'git branch branch-name' to mark a commit.
Switch to a branch with 'git checkout branch-name' to work there.
Use 'git log --oneline --decorate' to see commits and which branches point to them.

Practice

(1/5)
1. What is a branch in Git?
easy
A. A backup of the entire repository
B. A pointer to a specific commit in the project history
C. A copy of all files in the project
D. A remote server where code is stored

Solution

  1. Step 1: Understand what a branch represents

    A branch in Git is not a copy of files but a reference to a commit.
  2. Step 2: Identify the correct description

    The branch points to a specific commit, allowing you to work on different versions safely.
  3. Final Answer:

    A pointer to a specific commit in the project history -> Option B
  4. Quick Check:

    Branch = pointer to commit [OK]
Hint: Remember: branch points, not copies files [OK]
Common Mistakes:
  • Thinking a branch copies all project files
  • Confusing branch with remote repository
  • Assuming branch is a backup
2. Which of the following commands correctly creates a new branch named feature in Git?
easy
A. git branch feature
B. git create branch feature
C. git new branch feature
D. git checkout feature

Solution

  1. Step 1: Recall the Git syntax for creating branches

    The correct command to create a branch is git branch <branch-name>.
  2. Step 2: Check each option

    Only git branch feature matches the correct syntax.
  3. Final Answer:

    git branch feature -> Option A
  4. Quick Check:

    Create branch = git branch [OK]
Hint: Use 'git branch' to create branches [OK]
Common Mistakes:
  • Using 'git create branch' which is invalid
  • Using 'git new branch' which is not a Git command
  • Confusing 'git checkout' with branch creation
3. Given the following Git commands:
git commit -m "Initial commit"
git branch feature
What does the feature branch point to immediately after creation?
medium
A. No commit, branch is empty
B. An empty commit with no changes
C. The first commit in the repository
D. The latest commit on the current branch

Solution

  1. Step 1: Understand branch creation behavior

    When you create a branch, it points to the current commit you are on.
  2. Step 2: Analyze the commands

    After the initial commit, creating 'feature' branch points it to that latest commit.
  3. Final Answer:

    The latest commit on the current branch -> Option D
  4. Quick Check:

    New branch points to current commit [OK]
Hint: New branch points where you are now [OK]
Common Mistakes:
  • Thinking branch points to no commit
  • Assuming branch points to first commit always
  • Confusing branch with empty commit
4. You ran git branch new-feature but the branch is not the current branch (no asterisk) when you run git branch. What is the most likely reason?
medium
A. You created the branch but did not switch to it
B. The branch creation command was incorrect
C. The branch was created on a remote repository only
D. Git does not allow branch names with hyphens

Solution

  1. Step 1: Understand branch creation and listing

    Creating a branch with git branch adds it locally but does not switch to it.
  2. Step 2: Check why branch might not be current

    The branch appears in git branch list but without the * marker because you did not switch (git checkout) to it.
  3. Final Answer:

    You created the branch but did not switch to it -> Option A
  4. Quick Check:

    Branch created but not checked out [OK]
Hint: Create branch then checkout to use it [OK]
Common Mistakes:
  • Assuming branch creation switches branches
  • Thinking branch names cannot have hyphens
  • Confusing local and remote branches
5. You want to create a new branch experiment that starts from a commit with hash abc1234, without switching to it. Which command correctly does this?
hard
A. git checkout -b experiment abc1234
B. git branch -c experiment abc1234
C. git branch experiment abc1234
D. git create branch experiment abc1234

Solution

  1. Step 1: Understand how to create branch at specific commit

    Using git branch <name> <commit> creates a branch pointing to that commit without switching.
  2. Step 2: Check each option

    git branch experiment abc1234 matches. git checkout -b creates and switches. C and D are invalid.
  3. Final Answer:

    git branch experiment abc1234 -> Option C
  4. Quick Check:

    Create branch at commit = git branch name commit [OK]
Hint: Use 'git branch name commit' to start branch at commit [OK]
Common Mistakes:
  • Using invalid commands like 'git create branch'
  • Confusing branch creation with checkout
  • Using wrong flags like '-c' which does not exist