Bits of .NET

🐛 Key Takeaways: Git bisect helps you find the exact commit that introduced a bug. Binary search through history to identify the culprit in seconds.

Found a bug but don’t know when it was introduced? Git bisect finds the exact commit.

🚀 How to Use Git Bisect

# 1. Start bisect
git bisect start

# 2. Mark current commit as bad
git bisect bad

# 3. Mark known good commit
git bisect good abc1234  # Or use HEAD~100

# 4. Git checks out a commit in the middle
# "Bisecting: 50 revisions left to test after this (roughly 6 steps)"

# 5. Test the commit
dotnet test
# or manually test the application

# 6. Mark as good or bad
git bisect good
# or
git bisect bad

# 7. Repeat until culprit found!
# "abc5678 is the first bad commit"

💡 Scripted Bisect (Automated)

# ✅ Automated bisect with script
git bisect start
git bisect bad HEAD
git bisect good abc1234

# Test script that returns 0 for good, 1 for bad
git bisect run dotnet test

# Output:
# "abc5678 is the first bad commit"
# "bisect run success"

💡 Pro Tip: Visual Bisect

# See bisect status
git bisect visualize

# Show remaining commits
git bisect log

# Reset when done
git bisect reset

# Full workflow with script
#!/bin/bash
# bisect-bug.sh
git bisect start
git bisect bad HEAD
git bisect good $1  # Pass known good commit hash

# Test script
cat > test.sh << EOF
#!/bin/bash
dotnet test --filter "Category=Integration" > /dev/null 2>&1
if [ $? -eq 0 ]; then
    exit 0  # Good
else
    exit 1  # Bad
fi
EOF
chmod +x test.sh

git bisect run ./test.sh
git bisect reset