I just ran git-of-theseus on a repo that I help manage at work. Unfortunately, it's showing nearly all of the code as new this year and I think it's because we updated our Prettier config and reformatted most of our repo earlier this year
Git blame has the ability to ignore certain commit SHAs either using a file and the command, git blame --ignore-revs-file .git-blame-ignore-revs or by passing the SHAs and using the git blame --ignore-rev <SHA> option
It looks like git-of-theseus uses blame under the hood. Is it possible to add an option to either allow the user to pass the SHAs to ignore or to use the ignore revs file? Git also allows you to set a config for the repo using the blame.ignoreRevsFile option
I just ran git-of-theseus on a repo that I help manage at work. Unfortunately, it's showing nearly all of the code as new this year and I think it's because we updated our Prettier config and reformatted most of our repo earlier this year
Git blame has the ability to ignore certain commit SHAs either using a file and the command,
git blame --ignore-revs-file .git-blame-ignore-revsor by passing the SHAs and using thegit blame --ignore-rev <SHA>optionIt looks like git-of-theseus uses
blameunder the hood. Is it possible to add an option to either allow the user to pass the SHAs to ignore or to use the ignore revs file? Git also allows you to set a config for the repo using theblame.ignoreRevsFileoption