Requirements
To follow this setup, it is required to have following …
•
No Requirements
Debug [git bisect]
This command uses a binary search algorithm to find which commit in your project’s history introduced a bug. You use it by first telling it a "bad" commit that is known to contain the bug, and a "good" commit that is known to be before the bug was introduced. Then git bisect picks a commit between those two endpoints and asks you whether the selected commit is "good" or "bad". It continues narrowing down the range until it finds the exact commit that introduced the change.
Synopsis [git bisect --<synopsis>]
git bisect <subcommand> <options>
YAML
복사
Commonly Used Commands
•
Debugging
1.
git bisect start
2.
git bisect bad
3.
git checkout <hash address> to the suspicious commit
4.
git bisect good
5.
Until ends
a.
git bisect <good/bad>
6.
git bisect reset to end
