Lines Matching full:git

8 ``git bisect`` is a useful tool for finding which revision caused a bug.
10 This document describes how to use ``git bisect``. In particular, while LLVM
21 See https://git-scm.com/docs/git-bisect for a good overview. In summary:
25      git bisect start
26      git bisect bad main
27      git bisect good f00ba
29 git will check out a revision in between. Try to reproduce your problem at
30 that revision, and run ``git bisect good`` or ``git bisect bad``.
33 ``git bisect skip`` and git will pick a nearby alternate commit.
35 (To abort a bisect, run ``git bisect reset``, and if git complains about not
36 being able to reset, do the usual ``git checkout -f main; git reset --hard
39 ``git bisect run``
44 good if it can happen completely automatically. ``git bisect run`` can do
65 hand and tweak the script until it works, then run ``git bisect good`` or
66 ``git bisect bad`` manually once based on the result of the script
67 (check ``echo $?`` after your script ran), and only then run ``git bisect run
68 ./run.sh``. Don't forget to mark your run script as executable -- ``git bisect
71 Once your run script works, run ``git bisect run ./run.sh`` and a few hours
99 ``git bisect`` goes through all parent revisions. Due to the way MLIR was
103 As of early 2020, there is no flag to ``git bisect`` to tell it to not
107 The best workaround is to pass a list of directories to ``git bisect``:
112      git bisect start -- clang llvm compiler-rt
116 Alternatively, ``git bisect skip aed0d21a6 aed0d21a6..0f0d0ed1c78f`` explicitly
118 machine, and makes ``git bisect log`` output unreadable. (``aed0d21a6`` is
119 listed twice because git ranges exclude the revision listed on the left,
125 https://git-scm.com/book/en/v2/Git-Tools-Revision-Selection