Closed spenserblack closed 11 months ago
Oops :facepalm:
Bisected to 682adf8050f7566b4cef125515c1248c8e55736b
This also adds a .git-blame-ignore-revs file to ignore https://github.com/colored-rs/colored/pull/159/commits/d43dab0e09540b0cd2131db0161f4a0cfb0972ba in GitHub's blame view. This is especially helpful for formatting commits that can introduce "clutter" to the blame that doesn't describe actual behavioral changes. More info: https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view
.git-blame-ignore-revs
Just a heads-up that the .git-blame-ignore-revs file won't work if this PR is squash or rebase merged, since that would create a new commit hash.
Edit: now I see that "create merge commit" is disabled for this repo, so perhaps this .git-blame-ignore-revs file can go in a separate PR?
Fixed in another PR
Oops :facepalm:
Bisected to 682adf8050f7566b4cef125515c1248c8e55736b
This also adds a
.git-blame-ignore-revs
file to ignore https://github.com/colored-rs/colored/pull/159/commits/d43dab0e09540b0cd2131db0161f4a0cfb0972ba in GitHub's blame view. This is especially helpful for formatting commits that can introduce "clutter" to the blame that doesn't describe actual behavioral changes. More info: https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-viewJust a heads-up that the
.git-blame-ignore-revs
file won't work if this PR is squash or rebase merged, since that would create a new commit hash.Edit: now I see that "create merge commit" is disabled for this repo, so perhaps this
.git-blame-ignore-revs
file can go in a separate PR?