How can I cut down a git bisect run using file paths?

Question

I\'m using git bisect to find a failure inducing commit. However, a lot of the commits in the range are definately irrelevant (because they are commits to the documentation

Answer 1

You have several options here:

1. Ignoring specific commits

   git bisect contains functionality of skipping commits. You can specify commits, tags, ranges you don't want to test with

    git bisect skip 0dae5f ff049ab ...
   

   Just do this before you git bisect run, and it should skip what you specified.

2. Specifying folders with broken sources

   You can also cut down commits bisect tests by specifying what folders it should look for problems in. This is done at the beginning of bisect process by supplying additional arguments to git bisect start (quote from standard manual):

    git bisect start -- arch/i386 include/asm-i386
   

   Bisect will only consider commits that touch the folders specified.

---

If you want to automatically gather commits that touch certain files or folders, you may use git log for that. For example, the following command will give you commit names that modify files in certain folders:

git log --pretty=format:%H  tests/ docs/

And you can supply the result to git bisect skip with use of shell capabilities:

git bisect skip `git log --pretty=format:%H  tests/ docs/`