Handle exception when analyzing an empty repository #300
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It might seem obvious to run this tool on a non-empty repository, but for few use cases like integrating this tool as part of an automated pipeline to analyze several repositories there might be few empty repositories. When ran on an empty repository, it fails to
iter_commits
and throws the following error:To fix this, I followed the same approach adapted in
get_commits_modified_file
method to handle empty modifications by checkingGitCommandError
exception (ref). I have added the test case and added it's corresponding repository in the.zip
file.