Just an opinion that I wanted from some of you all...
# daft-dev
r
Just an opinion that I wanted from some of you all: The rustfmt PR will modify a whole bunch of lines. This will modify the git history, and I don't think there's a way around that. However, I think you can include a
.git-blame-ignore-revs
file in the file-tree which will be picked up by git and will ignore specific revisions, thus allowing git-blame to function as if a certain commit was not made (and thus allow the original imports to be appropriately git-blamed). We have two options: 1. Include the
.git-blame-ignore-revs
file in source-control. 2. Not include it in source-control and instead have the end-dev generate this file (will cause git-blame discrepancies across developers if one has a
.git-blame-ignore-revs
file and the other doesn't). Any opinions?
Leaning towards the former. Including it makes more sense. The end-user will have to run a
git config blame.ignoreRevsFile ...
for this to kick in, however.
s
It should work in GitHub automatically though
👍 1
r
I'll add it to this PR. Ya, it should work automatically on GitHub too.