#debugging with #git
▻https://hackernoon.com/debugging-with-git-b18600bbaa96?source=rss----3a8144eabfe3---4
When you are working on a huge project, you may discover bugs in the code that prevent you from proceeding any further in your development. How to fix them?You can start by looking through your commit history by hand, but this would end up as a very tedious process. Thankfully, Git has multiple tools that can help you hunt for a bug or the culprit when things go wrong.Git Blame$ git blame <file_path/file_name> The git blame command helps you find the commit that created the specific line of code that causes a bug in a specific file of a project. It also determines the author of the commit, making is easier to ask for more information about the code.You can -L option to limit the line output range.$ git blame -L 11,21 new_file^95d69a196b5c7 (Jhon Smith 2018-05-18 13:04:22 +0200 11) (...)