Hi Jeff, > Date: 2026-10-02 18:11:54-0400 > From: Jeff King > > 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. Thanks! It works. I guess the plumbing version of it would be git rev-list -1 bisect/bad right? > 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 Have a lovely day! Alex --