diff options
Diffstat (limited to 'src/content/tils/2020/11/12/git-bisect-automation.adoc')
| -rw-r--r-- | src/content/tils/2020/11/12/git-bisect-automation.adoc | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/src/content/tils/2020/11/12/git-bisect-automation.adoc b/src/content/tils/2020/11/12/git-bisect-automation.adoc index d7ea2ca..dff8737 100644 --- a/src/content/tils/2020/11/12/git-bisect-automation.adoc +++ b/src/content/tils/2020/11/12/git-bisect-automation.adoc @@ -10,11 +10,12 @@ I've already been in the situation when a bug was introduced and I didn't know how it even was occurring, and running Git bisect over hundreds of commits to pinpoint the failing commit was very empowering: -.... +[source,sh] +---- $ GOOD_COMMIT_SHA=e1fd0a817d192c5a5df72dd7422e36558fa78e46 $ git bisect start HEAD $GOOD_COMMIT_SHA $ git bisect run sn -c './build.sh && ./run-failing-case.sh' -.... +---- Git will than do a binary search between the commits, and run the commands you provide it with to find the failing commit. |