Différences

Ci-dessous, les différences entre deux révisions de la page.

--- tech:notes_git_bisect [2025/09/10 10:42] – Jean-Baptiste
+++ tech:notes_git_bisect [2026/06/07 19:12] (Version actuelle) – modification externe 127.0.0.1
@@ Ligne 1: / Ligne 1: @@
+<!DOCTYPE markdown>
+{{tag>Brouillon Git CA}}
+# Notes git bisect
+Voir aussi :
+  * http://bayledes.free.fr/systeme/git.html
+source : https://opensource.com/article/22/11/git-bisect
+Using Git bisect
+Using the git bisect command is very straightforward:
+~~~bash
+git bisect start
+git bisect bad        # Git assumes you mean HEAD by default
+git bisect good <ref> # specify a tag or commit ID for <ref>
+~~~
+Git checks out the commit in the middle and waits for you to declare either:
+~~~bash
+git bisect good
+## or
+git bisect bad
+~~~
+Then the bisect tool repeats checking out the commit halfway between good and bad commits until you tell it:
+~~~bash
+git bisect reset
+~~~
+Advanced users can even write scripts that determine good and bad states as well as any remediation actions to take upon finding the specific commit. You might not use the git bisect command every day of your life, but when you need it, it is a lifesaver.