Re: FYI, git output messages are being used by other tooling

[Junio C Hamano]

"Theodore Tso" <tytso@xxxxxxx> writes:

> A structured output that contained the result of the "git bisect
> good|bad", and the first bad commit if it has been found, would be
> certainly be a more reliable way for automated git bisection harneses
> to rely upon.  It'd be great if that was something that was in git
> 3.0.

I am afraid that anything we propose today would be too late for the
3.0 breaking changes list, but a new optional feature does not have
to wait for 3.0 at all ;-) I do not know if the format to do so
should be .jsonl or .yaml or what, but I agree that machine-readable
status output would be a helpful addition for automation.

Thanks.