Why rebasing creates linear history in Git - Quick Recap

Recall & Review

beginner

What does rebasing do to your commit history in Git?

Rebasing moves your branch's commits to start from the latest commit of the target branch, creating a straight, linear sequence of commits.

intermediate

How does rebasing differ from merging in terms of commit history?

Merging combines branches by creating a new merge commit, preserving the branch structure, while rebasing rewrites commits to create a linear history without merge commits.

beginner

Why is a linear history beneficial in Git?

A linear history is easier to read and understand because it shows a clear, step-by-step progression of changes without complex branching paths.

intermediate

What happens to your commits during a rebase?

Your commits are temporarily saved, the branch is moved to the new base commit, then your commits are reapplied one by one on top of that base.

intermediate

Can rebasing change commit hashes? Why?

Yes, because rebasing creates new commits based on the old ones but with a different parent, resulting in new commit hashes.

What is the main effect of rebasing a branch in Git?

A It deletes all commits on the branch.

B It creates a linear commit history by moving commits.

C It merges two branches with a merge commit.

D It creates a new branch without commits.

Rebasing moves commits to a new base, making the history linear.

Which Git command rewrites commit history to be linear?

A git merge

B git stash

C git clone

D git rebase

git rebase reapplies commits on top of another base commit, creating linear history.

What does rebasing do to commit hashes?

A Changes them because commits are recreated

B Deletes them

C Keeps them the same

D Merges them

Rebasing creates new commits with new hashes because the parent commit changes.

Why might developers prefer rebasing over merging?

A To delete branches

B To create more merge commits

C To keep a clean, linear history

D To avoid pushing changes

Rebasing keeps history simple and linear, making it easier to follow.

What happens to your commits during a rebase?

A They are saved, branch is moved, then reapplied

B They are deleted permanently

C They are merged into one commit

D They are pushed to remote automatically

Git saves your commits, moves the branch, then reapplies commits on top.

Explain in your own words why rebasing creates a linear history in Git.

Think about how commits are moved and reapplied on top of another branch.

Describe the difference between rebasing and merging regarding commit history.

Consider how each command affects the shape of the commit graph.