Allow the database file to live in a nested subdirectory #54
+2
−2
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.
I was running essentially
git-history file data/pipelines.db data/pipelines.json
and getting empty databases. Iterating overcommit.tree.blobs
only looks for files in the top level directory. Since my data was nested, I needed to iterate overcommit.tree.trees
also. According to some experimentation and the python-git docs, this path-like syntax should work for deeply nested files.