What a branch is (pointer to a commit) in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a branch in Git?

A branch in Git is a pointer to a specific commit. It helps you keep track of different lines of work in your project.

beginner

How does a branch pointer work in Git?

A branch pointer moves forward automatically when you make new commits, always pointing to the latest commit on that branch.

beginner

Why use branches in Git?

Branches let you work on new features or fixes separately without changing the main code. This keeps work organized and safe.

beginner

What happens when you switch branches in Git?

Switching branches changes your working files to match the commit the branch points to, letting you work on different versions easily.

beginner

How can you see all branches in a Git repository?

Use the command git branch to list all branches and see which one you are currently on.

What does a Git branch point to?

A A specific commit

B A file

C A folder

D A remote server

A Git branch is a pointer to a specific commit in the repository.

What happens to a branch pointer when you make a new commit on that branch?

A It creates a new branch

B It stays on the old commit

C It deletes the old commit

D It moves to the new commit

The branch pointer moves forward to the new commit automatically.

Which command shows all branches in your Git repository?

A git status

B git commit

C git branch

D git push

The command git branch lists all branches.

Why do developers use branches in Git?

A To work on features separately

B To delete files

C To speed up the computer

D To backup the entire project

Branches allow working on new features or fixes without affecting the main code.

What does switching branches do to your working files?

A Uploads files to the cloud

B Changes them to match the branch's commit

C Deletes all files

D Creates a new file

Switching branches updates your files to match the commit the branch points to.

Explain what a branch is in Git and how it relates to commits.

Think of a branch as a label that moves along your project history.

Describe why using branches is helpful when working on a project.

Imagine working on different tasks without mixing them up.

Practice

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