git-bisect

Understanding the Git Workflow article says, So you add a new rule: “When you merge in your feature branch, use –no-ff to force a new commit.” This gets the job done, and you move on. Then one day you discover a critical bug in production, and you need to track down when it was introduced. You run bisect but keep landing on checkpoint commits. You give up and investigate by hand. You narrow the bug to a single file. You run blame to see how it changed in the last 48 hours. You know it’s impossible, but blame reports the file hasn’t been touched in weeks. It turns out blame reports changes for

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 or to unit tests). I'd like to make git bisect automatically skip commits which affect files in certain directories. Is this possible somehow? You have several options here: 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

I'm aware that git bisect is branch-aware by design, so that if between good commit, G, and bad commit, B, you merged in a branch, it needs to take those changes into consideration as well, as the bug may be contained in the branch. In my case I have a dependency as a side branch and I merge in changes to my main project from time to time. The dependency can be considered a library that has a different way of running, different build-system etc. from my main project, but I still want recent changes from it via merges to the main branch. The problem is then that while bisecting in this scenario

I have read some articles saying that git bisect is awesome. However, I'm not a native speaker and I can't understand why it's awesome. Could someone please demonstrate with some code sample: How to use it? Is it just like svn blame ? The idea behind git bisect is to perform a binary search in the history to find a particular regression. Imagine that you have the following development history: ... --- 0 --- 1 --- 2 --- 3 --- 4* --- 5 --- current You know that your program is not working properly at the current revision, and that it was working at the revision 0 . So the regression was likely