Next: Visiting Blobs, Previous: References Buffer, Up: Inspecting [Contents][Index]
Also see the git-bisect(1) manpage.
magit-bisect-popup
)This prefix command shows the following suffix commands in a popup buffer.
When bisecting is not in progress, then the popup buffer features the following commands.
magit-bisect-start
)Start a bisect session.
Bisecting a bug means to find the commit that introduced it. This command starts such a bisect session by asking for a known good and a bad commit.
magit-bisect-run
)Bisect automatically by running commands after each step.
When bisecting is in progress, then the popup buffer features these commands instead.
magit-bisect-bad
)Mark the current commit as bad. Use this after you have asserted that the commit does contain the bug in question.
magit-bisect-good
)Mark the current commit as good. Use this after you have asserted that the commit does not contain the bug in question.
magit-bisect-skip
)Skip the current commit. Use this if for some reason the current commit is not a good one to test. This command lets Git choose a different one.
magit-bisect-reset
)After bisecting, cleanup bisection state and return to original
HEAD
.
By default the status buffer shows information about the ongoing bisect session.
This option controls whether a graph is displayed for the log of commits that still have to be bisected.
Next: Visiting Blobs, Previous: References Buffer, Up: Inspecting [Contents][Index]