Looks right to me. At t=0:50 it shows other git bisect commands being run. The git biset reset at the end is ending bisection as it's complete.

But what is that actually doing? It looks like when it's running the git bisect, it already knows what the commit is, and could have just returned it. The only reason it ran any bisecting at all, was because the user (erroneously) asked it specifically to use git bisect. It didn't have to.