0
0
Gitdevops~10 mins

git bisect run for automated bisect - Interactive Code Practice

Choose your learning style9 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the command to start a git bisect session.

Git
git bisect [1]
Drag options to blanks, or click blank then click option'
Alog
Brun
Creset
Dstart
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'run' instead of 'start' to begin bisect.
2fill in blank
medium

Complete the command to mark a commit as bad in git bisect.

Git
git bisect [1]
Drag options to blanks, or click blank then click option'
Areset
Bbad
Cskip
Dgood
Attempts:
3 left
💡 Hint
Common Mistakes
Marking bad commits as 'good' by mistake.
3fill in blank
hard

Fix the error in the command to run an automated test script during bisect.

Git
git bisect [1] ./test_script.sh
Drag options to blanks, or click blank then click option'
Arun
Bstart
Creset
Dlog
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'start' instead of 'run' to execute the script.
4fill in blank
hard

Fill both blanks to mark the known good and bad commits before running bisect.

Git
git bisect start
git bisect [1]
git bisect [2] <good-commit>
Drag options to blanks, or click blank then click option'
Abad
Bgood
Creset
Drun
Attempts:
3 left
💡 Hint
Common Mistakes
Swapping the order of good and bad commits.
5fill in blank
hard

Fill all three blanks to create a dictionary comprehension that filters commits by message length and keyword.

Git
filtered = [1]: commit for commit in commits if len(commit.message) [2] 50 and '[3]' in commit.message
Drag options to blanks, or click blank then click option'
Acommit.hash
B<
Cfix
Dcommit
Attempts:
3 left
💡 Hint
Common Mistakes
Using commit object as key instead of commit hash.