Git Bisect
Git bisect uses binary search through commit history to find the first commit where a repeatable behavior changed.
Another example
A bug has one known-good tag, one bad commit, and a test script that always gives the same answer. Bisect finds the first bad commit and the script confirms it. A test that fails at random makes the result unreliable.
Main parts
- 01known good
- 02known bad
- 03deterministic predicate
Use it when
Use this term when a bug repeats and you know one good commit and one bad commit around it.
Do not use it when
Do not bisect with unstable checks. If some commits cannot build, plan how to skip them.
Name used in code
git bisect start <bad> <good> Before you ship
Before publishing, check the exact repository, branch, target, and diff. Keep unpublished work. Pass review and CI checks. Record conflict and data-loss risks, release order, traceability, recovery, and rollback.
Outcome: Use Git Bisect to release or recover the change safely, with a clear record. User context: A bug has one known-good tag, one bad commit, and a test script that always gives the same answer. Bisect finds the first bad commit and the script confirms it. A test that fails at random makes the result unreliable. Delivery concept or operation: Git Bisect. Why it fits: Use this term when a bug repeats and you know one good commit and one bad commit around it. Do not use it when: Do not bisect with unstable checks. If some commits cannot build, plan how to skip them. Delivery requirements: Name the code repository and target. List preconditions, changes, review and CI checks, conflict and data-loss risks, release order, and the rollback or recovery command. Repository safeguards: Keep unpublished work and a clear history. Do not run destructive steps without an explicit backup. Check the exact code diff and remote target before publishing. Acceptance criteria: Review the intended diff and pass all required checks. Keep the target version traceable. Practice failure recovery and keep published history clear. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Repository, branch, team activity, release environment, approval owner, protected checks, and rollback target.
Check this request
Review the current use of Git Bisect. Definition: Git bisect uses binary search through commit history to find the first commit where a repeatable behavior changed. Release checks: Before publishing, check the exact repository, branch, target, and diff. Keep unpublished work. Pass review and CI checks. Record conflict and data-loss risks, release order, traceability, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.