@kernellogger If you want to describe that in the documentation:
Once you provided both a good and a bad version for git bisect, it will checkout automatically a commit in between. You don't have to test this commit: you may want to manually checkout a closer release tag, to avoid running into unrelated problems which got resolved after the merge window.