Uploaded September 2024 | Updated September 2026, 2 weeks ago
My keyboard: https://adm42.dev/?ref=3
We take a look at using the git bisect command to track down the commit responsible for breaking something, and we also look at how we can incorporate unit testing in this process to make it even easier.
Get weekly content and tips exclusive to my newsletter: https://mobirony.ck.page/4a331b9076
MY GEAR:
Neovim setup: github.com/joshuamorony/lazyvim
Animations: motioncanvas.io
0:00 Introduction
0:55 Using git bisect
2:12 Using tests with git bisect
#git #bisect
- More tutorials: modernangular.com
- Follow me on Twitter: twitter.com/joshuamorony
My keyboard: https://adm42.dev/?ref=3
We take a look at using the git bisect command to track down the commit responsible for breaking something, and we also look at how we can incorporate unit testing in this process to make it even easier.
Get weekly content and tips exclusive to my newsletter: https://mobirony.ck.page/4a331b9076
MY GEAR:
Neovim setup: github.com/joshuamorony/lazyvim
Animations: motioncanvas.io
0:00 Introduction
0:55 Using git bisect
2:12 Using tests with git bisect
#git #bisect
- More tutorials: modernangular.com
- Follow me on Twitter: twitter.com/joshuamorony










