@@ -452,34 +452,26 @@ <h2 id="_name">NAME</h2>
452452< h2 id ="_synopsis "> SYNOPSIS</ h2 >
453453< div class ="sectionbody ">
454454< div class ="verseblock ">
455- < pre class ="content "> < em > git bisect</ em > <subcommand> <options></ pre >
455+ < pre class ="content "> < em > git bisect</ em > start [--term-(bad|new)=<term-new> --term-(good|old)=<term-old>]
456+ [--no-checkout] [--first-parent] [<bad> [<good>…​]] [--] [<pathspec>…​]
457+ < em > git bisect</ em > (bad|new|<term-new>) [<rev>]
458+ < em > git bisect</ em > (good|old|<term-old>) [<rev>…​]
459+ < em > git bisect</ em > terms [--term-(good|old) | --term-(bad|new)]
460+ < em > git bisect</ em > skip [(<rev>|<range>)…​]
461+ < em > git bisect</ em > next
462+ < em > git bisect</ em > reset [<commit>]
463+ < em > git bisect</ em > (visualize|view)
464+ < em > git bisect</ em > replay <logfile>
465+ < em > git bisect</ em > log
466+ < em > git bisect</ em > run <cmd> [<arg>…​]
467+ < em > git bisect</ em > help</ pre >
456468</ div >
457469</ div >
458470</ div >
459471< div class ="sect1 ">
460472< h2 id ="_description "> DESCRIPTION</ h2 >
461473< div class ="sectionbody ">
462474< div class ="paragraph ">
463- < p > The command takes various subcommands, and different options depending
464- on the subcommand:</ p >
465- </ div >
466- < div class ="literalblock ">
467- < div class ="content ">
468- < pre > git bisect start [--term-(bad|new)=<term-new> --term-(good|old)=<term-old>]
469- [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...]
470- git bisect (bad|new|<term-new>) [<rev>]
471- git bisect (good|old|<term-old>) [<rev>...]
472- git bisect terms [--term-(good|old) | --term-(bad|new)]
473- git bisect skip [(<rev>|<range>)...]
474- git bisect reset [<commit>]
475- git bisect (visualize|view)
476- git bisect replay <logfile>
477- git bisect log
478- git bisect run <cmd> [<arg>...]
479- git bisect help</ pre >
480- </ div >
481- </ div >
482- < div class ="paragraph ">
483475< p > This command uses a binary search algorithm to find which commit in
484476your project’s history introduced a bug. You use it by first telling
485477it a "bad" commit that is known to contain the bug, and a "good"
@@ -804,6 +796,23 @@ <h3 id="_bisect_skip">Bisect skip</h3>
804796</ div >
805797</ div >
806798< div class ="sect2 ">
799+ < h3 id ="_bisect_next "> Bisect next</ h3 >
800+ < div class ="paragraph ">
801+ < p > Normally, after marking a revision as good or bad, Git automatically
802+ computes and checks out the next revision to test. However, if you need to
803+ explicitly request the next bisection step, you can use:</ p >
804+ </ div >
805+ < div class ="listingblock ">
806+ < div class ="content ">
807+ < pre > $ git bisect next</ pre >
808+ </ div >
809+ </ div >
810+ < div class ="paragraph ">
811+ < p > You might use this to resume the bisection process after interrupting it
812+ by checking out a different revision.</ p >
813+ </ div >
814+ </ div >
815+ < div class ="sect2 ">
807816< h3 id ="_cutting_down_bisection_by_giving_more_parameters_to_bisect_start "> Cutting down bisection by giving more parameters to bisect start</ h3 >
808817< div class ="paragraph ">
809818< p > You can further cut down the number of trials, if you know what part of
@@ -1091,7 +1100,7 @@ <h2 id="_git">GIT</h2>
10911100</ div >
10921101< div id ="footer ">
10931102< div id ="footer-text ">
1094- Last updated 2025-06-20 18:10:42 -0700
1103+ Last updated 2025-11-06 07:08:28 -0800
10951104</ div >
10961105</ div >
10971106</ body >
0 commit comments