Explore >> Select a destination
|
You are here 
|
nickjanetakis.com | ||
| | | | |
abuisman.com
|
|
| | | | | Blog about solving problems with code, mostly Ruby, and other things I have learned working as an engineer and a technical leader | |
| | | | |
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. | |
| | | | |
www.metaltoad.com
|
|
| | | | | The slowest, most tedious way of finding a bad git commit is something we've all done before. You checkout some old commit, make sure the broken code isn't there, then checkout a slightly newer commit, check again, and repeat over and over until you find the flawed commit. Using git bisect is a much better way. It's like a little wizard that walks you through recent commits, asks you if they are good or bad, and narrows down the broken commit. In this blog post, I encourage you to create a fresh git repo... | |
| | | | |
kennyballou.com
|
|
| | | Resurrect Lost History from the Information Manager from Hell | ||
