Open JacobPitts opened 7 years ago
Of interest, git log --follow sample.txt
also omits commit iteration 4, while git log sample.txt
shows all 5 commits.
Did you find any resolution to this problem?
Also interested in resolving of this issue. I use the library to dynamically update the file changes history; I noticed that merges are not included in history.
I was playing around with using CommitLog.QueryBy() to obtain the history of a specific file, and I am not clear if I'm using the feature correctly, but not getting the output I would expect.
Specifically, in a sample repo with 5 commits where each commit changes the same file, .QueryBy() appears to omit the commit that is merging and changing the file.
Is it possible this is by design, and the merge change in Iteration 4 is being purposefully omitted, or might this be a bug?
Here's the output of my sample program:
Here's the code that i'm running against a sample repo (see below):
Here's the script to create a sample git repo that has a diamond pattern of commits around a file: