[TheCoreh]

When using `git bisect` to find a bug, `git bisect good` and `git bisect bad` are not the only options available, there's also `git bisect skip`. You should only mark as bad commits that specifically manifest the bug you're looking for and not, say, build errors or other unrelated bugs. It is true however that the type of build breakage potentially brought in by using git rebase will require you to do more bisect steps.

[ris]

> It is true however that the type of build breakage potentially brought in by using git rebase will require you to do more bisect steps.

Or leave you with an inconclusive result if the guilty commit also happens to be one of the skipped commits