git bisect should return 1 when the first bad commit is found

Hi I'm using git bisect, and for complex reasons I can't use git bisect run to drive the bisection. I don't think git bisect bad/good is returning a different status code when the first bad commit is found and this would be very useful to stop the driver of the bisection. What do you think? Woul

Re: git bisect should return 1 when the first bad commit is found

eturn code and having the HEAD left to the original bad commit. Pedro. On Thu, Jun 13, 2019 at 11:22 AM Junio C Hamano wrote: > > Pedro Larroy writes: > > > I'm using git bisect, and for complex reasons I can't use git bisect > > run to drive the bisection.