chore(git-blame): add a revs ignore file for git blame#2649
Merged
Conversation
mariocynicys
force-pushed
the
clean-blame
branch
from
4f0c06f to
9ff91dd
Compare
shamardy
approved these changes
Nov 5, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
adds a
.git-blame-ignore-revsfile with a couple of toolchain upgrade commits that keep popping up a lot for me with each blame peek (using gitlens on vscode).whenever i wanna read the commit message associated with some line or take a quick look at the diff of the commit that introduced a certain line, i face one of these commits in the blame view and gotta pass by them and back to the original line change.
this is probably not all the commits that should be ignored, we might have other fmt/clippy/renamings commits, but these are the most prominent ones that keep popping up for me.