4.2.1.bisect

• 1.Introduction

  • Sometimes your project occur some accident (or bug) so that you need to trace back to find out the bug was caused from which commit

  • Git provides git bisect which was the tool to find the commit efficiently

  • This section records the bisect usage of TortoiseGit

• 2.Getting started

  • 1.You must to have idea that Which commit was good (the bug did not occur) and which was bad (the bug did occur) before performing bisect.

  • 2.Open the solution folder and right click on it, choose TortoiseGit -> Bisect start
  • 3.TortoiseGit will prompt a window and you must input the good commit and bad commit that you know.
  • 4.Input those commits and click OK.
  • 5.TortoiseGit to the commit between good one and bad one.
  • 6.Test current commit, mark Bisect good if good and vice versa.
  • 7.Repeat step.6 and TortoiseGit will help you to find the last good one

• 3.Reference

  • https://tortoisegit.org/docs/tortoisegit/tgit-dug-bisect.html