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
i have a private repo developed with other people, in which someone else deleted and recommitted some files. it make the gitlens blame in line showing that the recommitted files is committed by the latest guy. It makes me comfused.
when i use git blame to blame the file, it's truly showing all the lines werer committed by the guy. However, when i add git blame option with commit SHA hash before he committed, the blame result become read-able.
so i find the gitlens documentation and options, i found gitlens.advanced.blame.customArguments, so i add option in the setting.json like
{
// other options"gitlens.advanced.blame.customArguments": [
// "xxxxxx"
]
}
the xxxxxx is the SHA hash, the setting is global, which make it do not work with other files which is not deleted and recommitted.
i hope gitlens can support git blame hook, it work with giving the blame file name, then output blame options.
The text was updated successfully, but these errors were encountered:
i have a private repo developed with other people, in which someone else deleted and recommitted some files. it make the gitlens blame in line showing that the recommitted files is committed by the latest guy. It makes me comfused.
when i use
git blame
to blame the file, it's truly showing all the lines werer committed by the guy. However, when i add git blame option with commit SHA hash before he committed, the blame result become read-able.so i find the gitlens documentation and options, i found
gitlens.advanced.blame.customArguments
, so i add option in thesetting.json
likethe
xxxxxx
is the SHA hash, the setting is global, which make it do not work with other files which is not deleted and recommitted.i hope gitlens can support git blame hook, it work with giving the blame file name, then output blame options.
The text was updated successfully, but these errors were encountered: