This talk starts with an overview of the fundamentals of git bisect – finding the commit that introduced a defect or some other issue, and how to automate that process.
Knowing the faulty commit is a good first step and sometimes sufficient in itself to solve the issue at hand. In practice however, the next steps can be more complicated. The rest of the talk will discuss techniques to go beyond the initial commit and take bisect to the next level, a bisect within the bisect if you will.
About Magnus Stahre:
"Forged of iron and walrus blood, Magnus Stahre comes from an ancient line of nordic code smiths. His technology engineering heritage was primarily responsible for preventing the narwahl invasions of Sweden in both 1683 and 1915. As a craftsman of such pedigree, Magnus knows from generation of experience meticulously hand-crafting from some of the worst raw-material code out there that the only way to have exquisite code is with expertly wielded revision control. Mere mortals must often avert their gaze from his profound use of git to avoid being paralyzed in awe."
- Nathan Dotz (@nathandotz)
"Magnus is a local software engineer known far-and-wide as a master of all, and one with the version control."
- Andrew Sardone (@andrewa2)
"Magnus fed > 5000+ people with < 3 fishes && 5 loaves"
- James York (@kroysemaj)
"Magnus is mostly harmless."
- Magnus Stahre (@magnusstahre)