This course provides a practical overview of three different Git commands to help you track down and identify when a bug was introduced into the code case of your Git repository.
When working on a large Git project, it’s not uncommon to come across code bugs that slow down or block your development process. In such instances, manually sifting through your commit history can be a challenging and time-consuming process. In this course, Git Debugging Techniques, you’ll learn about three Git commands with different techniques that you can use to track down and identify when a bug was introduced into your codebase. First, you’ll learn how to debug your code through file history using Git Blame. Next, you’ll discover how to search through your codebase by binary search using Git Bisect. Last, you’ll see how to search for a string or regular expression using Git Grep. At the end of this course, you’ll gain experience using several different Git debugging techniques that you can use to locate and fix bugs within your codebase.
When working on a large Git project, it’s not uncommon to come across code bugs that slow down or block your development process. In such instances, manually sifting through your commit history can be a challenging and time-consuming process. In this course, Git Debugging Techniques, you’ll learn about three Git commands with different techniques that you can use to track down and identify when a bug was introduced into your codebase. First, you’ll learn how to debug your code through file history using Git Blame. Next, you’ll discover how to search through your codebase by binary search using Git Bisect. Last, you’ll see how to search for a string or regular expression using Git Grep. At the end of this course, you’ll gain experience using several different Git debugging techniques that you can use to locate and fix bugs within your codebase.
