From c52c742b2d6d8bb46ebe0f9db40499a1819dfd10 Mon Sep 17 00:00:00 2001 From: bleeptrack Date: Thu, 14 Jan 2021 11:43:26 +0100 Subject: [PATCH] bisect: level description clarification --- levels/bisect/bisect | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/levels/bisect/bisect b/levels/bisect/bisect index 4a25792..ec364b5 100644 --- a/levels/bisect/bisect +++ b/levels/bisect/bisect @@ -9,7 +9,7 @@ Oh no! You have lost your key at some point during the day! Sure, you could look at every single commit in an attempt to find it - but there's a better way: your time machine has a built-in way to find the point in time where things went wrong quickly! -First, play the "bisect start" card. Then, go to a commit where you don't have the key, and play the "bisect bad" card. Likewise, go to a commit early on where you have the key, and play the "bisect good card". +First, play the "bisect start" card. Then, go to a commit where you don't have the key, and play the "bisect bad" card. Likewise, go to a commit early on where you have the key *in your pocket*, and play the "bisect good card". After you've found the last good commit, reset the main branch to it. What happened to the key after you lost it? @@ -35,6 +35,7 @@ done [win] +# Find the last good commit test "$(git log --pretty=%s main | head -1)" -eq 17 [congrats]