From 0ea34e6bd9072873bccba629dadf1e454a8c4c06 Mon Sep 17 00:00:00 2001 From: Elatronion Date: Wed, 16 Feb 2022 21:38:05 -0500 Subject: [PATCH] fix typo in bisect level Yellow brick road `"bisect good card"` has been changed to `"bisect good" card` to be more accurate and consistent with `"bisect start" card` and `"bisect bad" card`. --- levels/bisect/bisect | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/levels/bisect/bisect b/levels/bisect/bisect index 0b66edb..cf7bf6a 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 *in your pocket*, 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?