Why rebasing creates linear history in Git - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the command to start rebasing the current branch onto main.

Git

git rebase [1]

Drag options to blanks, or click blank then click option'

Adevelop

Bmain

Cfeature

Dorigin

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong branch name like 'feature' or 'origin' instead of 'main'.

Confusing rebase with merge commands.

The command git rebase main moves your current branch changes on top of the latest main branch commits, creating a linear history.

2fill in blank

medium

Complete the command to abort a rebase in progress.

Git

git rebase --[1]

Drag options to blanks, or click blank then click option'

Acontinue

Bskip

Cabort

Dedit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'continue' which tries to proceed with the rebase.

Using 'skip' which skips the current patch.

The command git rebase --abort stops the rebase process and returns the branch to its original state before rebasing.

3fill in blank

hard

Fix the error in the command to rebase interactively.

Git

git rebase -[1] main

Drag options to blanks, or click blank then click option'

Ai

Ba

Cm

Dr

Attempts:

3 left

💡 Hint

Common Mistakes

Using flags like '-a' or '-m' which are not valid for rebase.

Forgetting the dash before the flag.

The -i flag starts an interactive rebase, letting you edit commits before applying them.

4fill in blank

hard

Fill both blanks to create a linear history by rebasing and then pushing with force.

Git

git rebase [1] && git push origin [2] --force

Drag options to blanks, or click blank then click option'

Amain

Bfeature-branch

Cmaster

Ddevelop

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the branch names for rebase and push.

Forgetting to use --force when pushing after rebasing.

First, you rebase your feature-branch onto main to create a linear history. Then you force push the rebased branch to update the remote.

5fill in blank

hard

Fill all three blanks to create a linear history dictionary comprehension filtering commits by author.

Git

commits = { [1]: [2] for [3] in commit_list if [3].author == 'Alice' }

Drag options to blanks, or click blank then click option'

Acommit.hash

Bcommit.message

Ccommit

Dcommit.id

Attempts:

3 left

💡 Hint

Common Mistakes

Using commit.id which may not exist.

Using the wrong variable name in the loop.

This dictionary comprehension creates a mapping from commit hashes to their messages, but only for commits authored by Alice, showing a filtered linear history.