Explore >> Select a destination
|
You are here 
|
nathanchance.dev | ||
| | | | |
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. | |
| | | | |
nickjanetakis.com
|
|
| | | | | This automates the process of doing a manual bisection search, AKA a binary search which helps quickly find 1 item in a list of items. | |
| | | | |
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. | |
| | | | |
blog.gitbutler.com
|
|
| | | What `git config` settings should be defaults by now? Here are some settings that even the core developers change. | ||
