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
In gitlab.nvim we are using diffview.nvim as the "reviewer" for Gitlab merge requests. I've noticed that Gitlab must be using a non-default threshold for similarity index for finding renames (git docs), I've got a file that was renamed and modified and Gitlab shows it as such, while Diffview shows the original file as deleted and a new file added. This is because the similarity index for the given file was 41, so I'm able to force Diffview into the same behaviour as Gitlab with this modification:
It would be nice if this option to Git would be configurable in Diffview, so that we could make gitlab.nvim behave as close to Gitlab as possible.
Note: There's already the possibility to configure the git_cmd in Diffview, but obviously, this cannot be set to something like git_cmd = {"git", "-M40%"}, because the -M40% option only makes sense for the diff subcommand.
The text was updated successfully, but these errors were encountered:
In gitlab.nvim we are using
diffview.nvim
as the "reviewer" for Gitlab merge requests. I've noticed that Gitlab must be using a non-default threshold for similarity index for finding renames (git docs), I've got a file that was renamed and modified and Gitlab shows it as such, while Diffview shows the original file as deleted and a new file added. This is because the similarity index for the given file was 41, so I'm able to force Diffview into the same behaviour as Gitlab with this modification:It would be nice if this option to Git would be configurable in Diffview, so that we could make
gitlab.nvim
behave as close to Gitlab as possible.Note: There's already the possibility to configure the
git_cmd
in Diffview, but obviously, this cannot be set to something likegit_cmd = {"git", "-M40%"}
, because the-M40%
option only makes sense for thediff
subcommand.The text was updated successfully, but these errors were encountered: