One of the results of expanding the RavenDB’s team is that we have to deal with a lot more pull requests. We have individual developers working on their features, and submitting pull requests on a daily basis. That usually means that I have to merge anything between ten to thirty pull requests per day.
Given our test suite runtime, it isn’t really reasonable to run the full test suite after each pull request, so we merge them all, review them, and then run the tests. The problem then is that if there was a test failure… which pull request, and which commit cause it?
That is why git has the wonderful git bisect command. And we have taken advantage of that to enable the following development time feature:
./bisect.ps1 HEAD HEAD~10 General_Initialized_WithoutErrors
It will output something like:
631caa60719b1a65891eec37c4ccb4673eb28d02 is the first bad commit
Author: Pawel Pekrol
Date: Fri May 9 08:57:55 2014 +0200
another temp commit
Pin pointing exactly where the issue is.
And yes, this is here as a post primarily because I might forget about it.