Currently, Git Hammer will mostly just let Python exceptions propagate upwards, which can make it very difficult to understand what exactly the problem is. An error from somewhere in the processing should at a minimum identify the problematic commit, any relevant file(s) and lines there, and give a better reason for why the error happened. This is probably not too difficult work, but setting up everything, especially the tests, seems like it can take a while.
Currently, Git Hammer will mostly just let Python exceptions propagate upwards, which can make it very difficult to understand what exactly the problem is. An error from somewhere in the processing should at a minimum identify the problematic commit, any relevant file(s) and lines there, and give a better reason for why the error happened. This is probably not too difficult work, but setting up everything, especially the tests, seems like it can take a while.