From 570ec471d1605318aeefb030cd78682ae442235b Mon Sep 17 00:00:00 2001 From: EuAndreh Date: Mon, 31 Mar 2025 21:51:40 -0300 Subject: src/content/: Update all files left to asciidoc --- .../tils/2020/11/12/git-bisect-automation.adoc | 23 +++++----------------- 1 file changed, 5 insertions(+), 18 deletions(-) (limited to 'src/content/tils/2020/11/12/git-bisect-automation.adoc') 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 9c34b2a..c70bb2d 100644 --- a/src/content/tils/2020/11/12/git-bisect-automation.adoc +++ b/src/content/tils/2020/11/12/git-bisect-automation.adoc @@ -1,18 +1,4 @@ ---- - -title: Git bisect automation - -date: 2020-11-12 2 - -layout: post - -lang: en - -ref: git-bisect-automation - -eu_categories: git - ---- += Git bisect automation It is good to have an standardized way to run builds and tests on the repository of a project, so that you can find when a bug was introduced by using @@ -22,14 +8,15 @@ 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: -``` +.... $ 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. Instead of being afraid of doing a bisect, you should instead leverage it, and -make Git help you dig through the history of the repository to find the bad code. +make Git help you dig through the history of the repository to find the bad +code. -- cgit v1.2.3