You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the compact summary doesn't have room to put the entire filename, it ends up being truncated. Git will change part of it to .... When that happens, git_diff_explorer can't find the actual file path in order to show the diff.
I've no idea what an entry would look like if it is a moved file and also truncated like this.
The text was updated successfully, but these errors were encountered:
Possible plan of attack.
Try to identify such entries by checking if they contain ... and don't exist.
In such cases, do the following:
Escape the entry for a regex.
Change the ... into .*.
Run the git diff --name-only command.
Grep those with the -x flag (--line-regexp, only matches whole lines) using the modified entry.
If only 1 entry is found, use that as the filename.
If zero entries are found, just go with the original entry.
If two or more entries are found, I'm not sure what to do. I'm tempted to just say to use all of them. I'm not sure how we'd be able to further refine the search.
When the compact summary doesn't have room to put the entire filename, it ends up being truncated. Git will change part of it to
...
. When that happens,git_diff_explorer
can't find the actual file path in order to show the diff.I've no idea what an entry would look like if it is a moved file and also truncated like this.
The text was updated successfully, but these errors were encountered: