From 13f5e45f4d3b6957a7a4facd07f97cf6bbc160ba Mon Sep 17 00:00:00 2001 From: "Arnaud M." Date: Tue, 23 Dec 2025 12:22:52 +0100 Subject: [PATCH] Fix the start version in bad-commit Signed-off-by: Arnaud M. --- bad-commit/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bad-commit/README.md b/bad-commit/README.md index d5bf92af..84e6926f 100644 --- a/bad-commit/README.md +++ b/bad-commit/README.md @@ -17,7 +17,7 @@ For this exercise, the version is bad if `badfile` exists. 1. Start `git bisect`. 2. Usually the HEAD is "bad", as it is in this exercise. Use `git bisect bad` to indicate it. -3. Usually some old version will be good. In this exercise, the start version is. Use `git bisect good ` to indicate it. +3. Usually some old version will be good. In this exercise, the start version is `63e1df85cb135e97e562c8f15f883bb4e5137e8c`. Use `git bisect good ` to indicate it. 4. `git bisect` will then checkout various commits to find the bad commit. Continue indicating the state until it tells you the first bad commit. Keep track of this commit. 5. Run `git bisect reset` so we can work on the repository. 6. Use `git diff` to make sure that the bad commit only introduced `badfile`.