Git's worktrees give you an extra working copy of your repository, and setting one up is almost as easy as creating a new branch.

I thought it might be informative to show a bit on how I pinpoint an offending commit to the repository.  In this case, the issue was reported in the 170 beta, and confirmed working in the 1.2.169 version.  Since I’ve reviewed all code coming into 170, I did have suspicions around what might have changed recently.  But still, I wanted to know if the problem was in bob.jar/editor or the engine.  This is to split the problem domain into much smaller pieces, and at the same time rule out large chun...