/explore
|
You are here 
|
danielrotter.at | ||
| | | | |
adamj.eu
|
|
| | | | | 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. | |
| | | | |
haacked.com
|
|
| | | | | 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. | |
| | | | |
citizen428.net
|
|
| | | | | 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: | |
| | | | |
yasoob.github.io
|
|
| | | |||
