BisectingFinding faulty commits

suggest change

Syntax

git bisect <subcommand> <options>
git bisect start <bad> [<good>...]
git bisect reset
git bisect good
git bisect bad

Found a mistake? Have a question or improvement idea? Let me know.

Bisecting to find faulty commits:

*BisectingFinding faulty commits

*Binary search git bisect

*Semi-automatically find a faulty commit

Table Of Contents

0Getting started

1Committing

2Browsing the history

3Undoing

4Staging

5Git diff

6Merging

7Ignoring files and folders

8Working with remotes

9Submodules

10Aliases

11Rebasing

12Configuration

13Branching

14rev-list

15Squashing

16Cherry picking

17Recovering

18git clean

19.gitattributes

20.mailmap

21Different workflows

22Pulling

23Hooks

24Cloning repositories

25Stashing

26Subtrees

27Renaming

28Pushing

29Internals

30git-tfs

31Empty directories in git

32git-svn

33Archive

34Rewriting history with filter-branc

35Migrating to git

36Show

37Resolving merge conflicts

38Bundles

39Display commit history graphically with gitk

40Bisecting to find faulty commits

41Blaming

42Git revisions syntax

43Worktrees

44Git remote

45Git large file storage

46git patch

47git statistics

48git send-email

49git gui clients

50reflog - restoring commits not shown in git log

51TortoiseGit

52External merge and diff tools

53Update object name in reference

54Git branch name on Bash Ubuntu

55Git client-side hooks

56Git rerer

57Change git repository name

58git tagging

59tidying up your local and remote repository

60diff tree

61Contributors