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.
This builds upon the incremental git-blame support, as added in #409. I realized that the previous implementation only returned a subset of all available information from the command's output (only the information I directly needed for my use case). However, that would mean that if we would like to use more of the available blame information, we would need to change the function's returned data structure.
Rather than a
(commit: Commit, linenos: Range)
tuple, this now outputs a stream ofBlameEntry
instances. These are named 4-tuples, containing the following fields:commit
linenos
orig_path
orig_linenos
Which adds the last 2 fields, providing information on the original filepath / original line numbers for these paths.
Hopefully, this future-proofs the blame_incremental output before the previous implementation gets released and needs to be supported, too.