Q: Production is broken. You know it worked at the v2.3 tag but not at HEAD, with about 200 commits between them. How do you find the exact commit that introduced the bug efficiently?
Use git bisect — a binary search over commits.
git bisect workflow, ability to automate root-cause analysis.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Want to master this scenario in a live sandbox? KodeKloud's Advanced Git Workflows, Rebase & Interactive Diagnostics covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "During a major release branch cut, we encountered this exact scenario and used Git internals to recover cleanly. The interviewer is testing: git bisect workflow, ability to automate root-cause analysis.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
Use git bisect — a binary search over commits. Git checks out a commit roughly halfway between them. You build/test it and report: Each step halves the search space. With 200 commits, you'll converge in ~8 steps (log2(200)). When done, Git prints "X is the first bad commit." Then: Automate it if you have a reproducer script that exits 0 (good) or non-zero (bad): Walk away — Git does the rest. Tips: skip commits that don't build with git bisect skip; use --first-parent if your history has many merge commits and you only care about which *merge* introduced the bug. Bisect works because every commit is an immutable snapshot, so each one is independently testable.
git bisect start
git bisect bad HEAD # tell Git the current commit is broken
git bisect good v2.3 # tell Git this old tag was fine
- Immediate Triage: Use git bisect — a binary search over commits.
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
-
Running raw git push --force rather than git push --force-with-lease on shared team feature branches when configuring broken know worked
git push --forceunconditionally overwrites remote commits made by teammates, whereas--force-with-leaseaborts if the remote ref was updated. - Resolving complex merge conflicts with blind checkout overwrite strategies without running unit tests when configuring broken know worked Unilateral conflict resolution frequently clobbers complementary logic introduced in parallel feature branches, creating regression bugs.
-
Discarding corrupted working directories prematurely instead of recovering lost state using git reflog when configuring broken know worked
git reflogtracks every HEAD movement, allowing instant recovery of discarded commits, botched rebases, or deleted local branches. - Disabling branch protection rules and mandatory PR approval reviews on shared release branches when configuring broken know worked Without branch protection, developers can bypass CI validation gates and push untested code directly to production branches.