git-bisect: add page #1227
git-bisect: add page #1227
Conversation
waldyrious
added
the
new command
|
|
||
| `git bisect reset` | ||
|
|
||
| - Skip a commit during a bisect (e.g. one that causes a broken build due to another issue): |
There was a problem hiding this comment.
Did not get this. Why would you need to skip a commit ? If its unrelated to the current bug, we can just mark it as good right ?
There was a problem hiding this comment.
If a commit is broken for a different reason, you may not be able to tell whether the issue you're looking for is present in it or not -- the idea here is to tell git bisect to ignore this commit rather than pass it as a data point, as that could be a false positive or a false negative, both of which would pollute the binary search process.
| > Use binary search to find the commit that introduced a bug. | ||
| > Git automatically jumps back and forth in the commit graph to progressively narrow down the faulty commit. | ||
|
|
||
| - Start a bisect section by passing a known good commit and a known bad commit: |
There was a problem hiding this comment.
I was slightly stumped in understanding "known bad commit". How can I know the bad commit if I have to find it in the first place ? Then it dawned on me, that its a commit sufficiently back in time so that the actual commit which introduced the bug is in the range.
Maybe we can rephrase it as - "Start a bisect section by passing a start and end commit which contains the commit we want to find".
There was a problem hiding this comment.
I think that makes sense. Will change.
ps - I just realized I meant to write "Start a bisect session", not "section"! Will fix that as well.
|
@agnivade I went through a lot of back-and-forth attempting to produce concise yet clear descriptions. I'm not sure I managed it; PTAL. |
|
Nicely done. 👍 |
No description provided.