diff options
| author | EuAndreh <eu@euandre.org> | 2024-11-18 08:21:58 -0300 |
|---|---|---|
| committer | EuAndreh <eu@euandre.org> | 2024-11-18 08:44:57 -0300 |
| commit | 960e4410f76801356ebd42801c914b2910a302a7 (patch) | |
| tree | 615d379416f72956d0c1666c63ce062859041fbe /src/content/tils/2020/11/12/git-bisect-automation.adoc | |
| parent | Remove jekyll infrastructure setup (diff) | |
| download | euandre.org-main.tar.gz euandre.org-main.tar.xz | |
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 | 35 |
1 files changed, 35 insertions, 0 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 new file mode 100644 index 0000000..9c34b2a --- /dev/null +++ b/src/content/tils/2020/11/12/git-bisect-automation.adoc @@ -0,0 +1,35 @@ +--- + +title: Git bisect automation + +date: 2020-11-12 2 + +layout: post + +lang: en + +ref: git-bisect-automation + +eu_categories: git + +--- + +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 +`git bisect run`. + +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. |