also do folks who use git bisect have any gotchas/tips that you wish you knew earlier when using bisect?
the main tip I've heard so far is that you can use --first-parent if you only want to bisect the top-level merge commits (in a project that uses merges)
@b0rk If you think you may have messed up (and your history is linear) because you keep getting "bad" commits: do git bisect log and retest the most recent "good" commit. And the reverse if you keep getting "good" commits.
I also like to do this as a final check after the bisect completes.
If you did mess up, you can use the output from git bisect log to restart your bisect without having to redo any tests.
Probably also applies when using --first-parent but I'm not familiar with it.
@madewokherd interesting! do you know what the 00000000000000s are about in the output of `git bisect log` here? i'm a bit perplexed
(i just ran `git bisect good` and `git bisect bad` at random a few times and it otherwise seems normal)
