/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 danielrotter.at
git bisect and the importance of a clean history | Daniel Rotter
| | haacked.com
Supercharge your debugging with git bisect | You've Been Haacked
10.8 parsecs away

Travel
| | Git bisect is an underrated but very powerful tool to include in your debugging toolbox. In short, it helps you find the commit that introduced a bug. Here's an example of how to use it.
| | adamj.eu
Git: the basics of git bisect - Adam Johnson
10.4 parsecs away

Travel
| | git bisect efficiently searches for a commit responsible for changing a given behaviour. git log lets you see when a given file or line changed, but that's often insufficient when the cause of some change is unclear. In such cases, git bisect shines, as it lets you check your running system.
| | citizen428.net
10 Common Git Problems and How to Fix Them - citizen428.net
10.6 parsecs away

Travel
| | I originally wrote this article for Codementor in October 2014. It should have something for everyone, from fairly new git users to experienced developers. 1. Discard local file modifications Sometimes the best way to get a feel for a problem is diving in and playing around with the code. Unfortunately, the changes made in the process sometimes turn out to be less than optimal, in which case reverting the file to its original state can be the fastest and easiest solution:
| | til.simonwillison.net
git bisect | Simon Willison's TILs
32.5 parsecs away

Travel
| I extracted and enhanced this TIL from my April 8th 2020 weeknotes to make it easier to find.