Using a pathspec that includes most magic (other than "top" and "literal") is not compatible with the --follow flag, whose documentation notes that it works only for a single file:
--follow
Continue listing the history of a file beyond renames (works
only for a single file).
This can be verified locally by running something like this in a git repository:
Using a pathspec that includes most magic (other than "top" and "literal") is not compatible with the --follow flag, whose documentation notes that it works only for a single file:
This can be verified locally by running something like this in a git repository:
The
--follow
flag should only be added whenvcs.CommitsOptions.Path
specifies a single file rather than an unsupported magic.More details are provided in the commit message of PR #111, which fixes this issue.