From: Alejandro Colomar <alx@kernel.org>
Date: Sat, 03 Oct 2026 10:10:44 GMT
Subject: git-visualize(1) plumbing equivalent
Message-ID: <asDTWsH-RuIJOyne@debian>

Hi!

I have this code, which I use to loop in a script using git-bisect(1):

	while
		git bisect visualize --oneline \
		| wc -l \
		| xargs -I{} test {} -gt 1;
	do
		if
			git rebase $gropts BISECT_HEAD >/dev/null 2>/dev/null;
			test $? -eq 0;
		then
			echo 'Rebase: success';
			git bisect good BISECT_HEAD;
		else
			echo 'Rebase: conflict';
			git rebase --abort >/dev/null;
			git bisect bad BISECT_HEAD;
		fi;
	done;

(
I know this resembles "git rebase run", but I'm avoiding it, because
passing all of that as a command is non-trivial (and I'd like to avoid
having to write a separate script to pass its name to "git bisect run").
)

Having read the documentation for git-bisect(1), visualize reads several
environment variables, and thus this code doesn't seem robust.  What
would be the plumbing version of the while-loop condition?

		git bisect visualize --oneline \
		| wc -l \
		| xargs -I{} test {} -gt 1;

The goal is to know whether git-bisect(1) has found a commit yet or not,
to stop looping.


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es>