Finding bugs

Even the best testing groups let bugs slip out into the field. When that happens, it's up to the developers to figure out what the bug is and how to fix it.

Git has tools to help.

Nobody deliberately creates bugs, so the problem is probably caused by fixing an old bug or adding a new feature.

If you can isolate the code that causes the issue, use the git blame command to find who committed the code that caused the problem and what the commit SHA code was.

How to do it...

The git blame command returns a list of commit hash codes, author, date, and the first line of the commit message:

$ git blame testGit.sh  
    d5f62aa1 (Flynt 2016-12-07 09:41:52 -0500 1) Created testGit.sh
    063d573b (Flynt 2016-12-07 09:47:19 -0500 2) Edited on master repo.
    2ca12fbf (Flynt 2016-12-07 10:03:47 -0500 3) Edit created remotely   
    and merged.

There's more...

If you have a test that indicates the problem, but don't know the line of code that's at issue, you can use the git bisect command to find...