anchor.diff:  [[pinpointing-regressions-with-git-bisect]]
   === Pinpointing Regressions with git bisect
   
  -If you've discovered a regression, it is helpful to identify and information
  +If you've discovered a regression, it is helpful to identify information
   regarding the first bad commit when reporting issues. This is easy to do by
   first depending on a checkout of ClojureScript as a local root dependency and
  -then using git bisect.
  +then using `git bisect`.
   
   For this example, let's say you've discovered a regression that is reproducible
   directly in the REPL (variations on the below can be employed if not).
  
positive.code: 
  Test to see if you can reproduce the issue in the REPL and then exit the REPL.
  
  If you couldn't reproduce the issue:
  
  [source,bash]
  ----
  git bisect good
  ----
  
  Or, if you were able to reproduce the issue:
  
  [source,bash]
  ----
  git bisect bad
  ----
  
  If the bisect is complete, git will indicate that a certain commit hash 
  "is the first bad commit". Copy all of this text for JIRA.
  
  Otherwise restart the REPL and repeat the above steps until done.
  
  When finished, you can do this to restore your git checkout:
  
  [source,bash]
  ----
  
negative.code: git bisect good r1.10.748
  ----
  
  Then (in another directory) start up a REPL against the current state of the 
  checkout tree by issuing:
  
  [source,bash]
  ----
  