Bisect for finding bug-introducing commits in Git - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to start bisecting from a known bad commit.

Git

git bisect [1] bad_commit_hash

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

Ainit

Brun

Cbegin

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'init' or 'begin' instead of 'start'.

Trying to run bisect without starting.

The command git bisect start starts the bisect session.

2fill in blank

medium

Complete the command to mark a commit as good during bisect.

Git

git bisect [1] good_commit_hash

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

Agood

Bstart

Cbad

Dskip

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'bad' instead of 'good'.

Using 'skip' when the commit is actually good.

Use git bisect good to mark a commit as good.

3fill in blank

hard

Fix the error in the command to mark a commit as bad during bisect.

Git

git bisect [1] bad_commit_hash

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

Abad

Bskip

Cstart

Dgood

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'good' instead of 'bad'.

Using 'start' which is invalid here.

Use git bisect bad to mark a commit as bad.

4fill in blank

hard

Fill both blanks to complete the command that ends bisect and returns to the original branch.

Git

git bisect [1] && git checkout [2]

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

Areset

Bstart

Cmain

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' or 'init' to end bisect.

Checking out a wrong branch name.

git bisect reset ends bisect mode, and git checkout main returns to the main branch.

5fill in blank

hard

Fill all three blanks to run a bisect session marking commits as good or bad automatically using a test script.

Git

git bisect [1] bad_commit_hash good_commit_hash && git bisect [2] ./test_script.sh && git bisect [3]

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

Astart

Brun

Creset

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'init' instead of 'start'.

Forgetting to reset after running bisect.

Using wrong commands for running the script.

First, git bisect start bad_commit_hash good_commit_hash starts bisect. Then git bisect run ./test_script.sh runs the test script automatically. Finally, git bisect reset ends the bisect session.