When you need to discover a regression, it's great to know when it happened! It's surprisingly easy to do with git bisect - You can find out what commit had a regression, and in the process you'll learn how to think carefully about how to define and solve the problem.
We'll cover:
- How simple it is to do the basic
git bisectto find out when something went wrong - How to do fancier things (like a composer install at the point of a piece of code, or a database import)
- How to make a simple script that will do all the work while you're having coffee or sleeping
It's easy. Take the little bit of time to master a great tool.
