From: Jeff King <peff@peff.net>
Date: Fri, 02 Oct 2026 22:11:54 GMT
Subject: Re: git-bisect(1) next after finding the commit
Message-ID: <20261002221154.GA833115@coredump.intra.peff.net>
In-Reply-To: <asAbOSQ4BkuCTPY5@debian>

On Fri, Oct 02, 2026 at 11:49:01PM +0200, Alejandro Colomar wrote:

> Is there a plumbing command for retrieving the bisected commit after
> a git-bisect(1) session has successfully found it (and of course before
> resetting the session)?
> 
> I expected `git bisect next` would bring me to it, and then I'd rev-list
> HEAD -1, but it doesn't bring me to it.

I'm not 100% sure, but I think "git show bisect/bad" should work.

As the bisection progresses, we advance a single refs/bisect/bad from
the bottom of the range (the top is multiple refs/bisect/good-* refs).
So at the end, it should point to the blamed commit.

-Peff