Finding a bad commit

Questions 1 to 5 of 8

1. 1. Put these steps in the order you run them to find the bad commit automatically with a test command.

   Use the arrows to put the steps in order.

   1. 1.git bisect bad HEAD↑↓
   2. 2.git bisect good HEAD~5↑↓
   3. 3.git bisect run python3 test_calc.py↑↓
   4. 4.git bisect reset↑↓
   5. 5.git bisect start↑↓
2. 2. Put these steps of one manual bisect check in order, starting when Git checks out a commit.

   Use the arrows to put the steps in order.

   1. 1.Run python3 test_calc.py and read the exit code with echo $?↑↓
   2. 2.Tell Git good or bad with git bisect good or git bisect bad↑↓
   3. 3.Git picks the next middle commit, until it names the first bad commit↑↓
   4. 4.Git checks out a commit in the middle of the range↑↓
3. 3. Which exit code makes git bisect run skip a commit that cannot be tested?

   01125126
4. 4. Why must you run git bisect reset when a bisect ends?

   It deletes the bad commit from the historyIt puts your folder back on the branch you started fromIt undoes the last good markIt pushes the result to GitHub
5. 5. What is the Git command that shows, for each line of a file, the last commit that changed it? Answer with the command name only.

   Type your answer.