Tracking down a bug in a large codebase can be frustrating. **Git bisect** helps by using a binary search to quickly find the exact commit that introduced the issue.
## Step 1: Start Git Bisect
Begin by starting bisect mode:
```sh
git bisect start
```
## Step 2: Mark a Good and Bad Commit
Specify a known working commit:
```sh
git bisect good a1b2c3d
```
Mark the current commit (where the bug exists) as bad:
```sh
git bisect bad
```
## Step 3: Test and Mark Commits
Git checks out a middle commit. Run your app and test it:
```sh
./gradlew bootRun
```
If the bug exists:
```sh
git bisect bad
```
If the bug is not present:
```sh
git bisect good
```
## Step 4: Find the Bad Commit
Once Git finds the problematic commit, it displays:
```sh
1234567 is the first bad commit
```
## Step 5: Reset Git Bisect
Once the issue is identified, reset bisect mode:
```sh
git bisect reset
```
## Conclusion
Using **git bisect** can save you hours when debugging! Instead of checking each commit manually, bisect efficiently pinpoints the issue in just a few steps.
Comments
Post a Comment