In my Git: The Next Steps course I talk about a powerful tool, git-bisect, for finding where code broken or an change happened that you're trying to track down. By default, git-bisect uses "good" and "bad" as a way to tell Git which commits don't have the issue and which do. But these terms aren't always relevant to what you're working on and that can lead to confusion. On its own, git-bisect can be a confusing tool when you first use it, so anything we can do to make it more sense, is a huge bonus. In this lesson we walk through how to change the terms from "good" and "bad" to something custom based on the problem we're working on.