-
Notifications
You must be signed in to change notification settings - Fork 576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ENH] add a .git-blame-ignore-revs
to ignore formatting PR from git blame
#3653
Comments
Let me know what you think. |
Also it seems to also work when using git blame via the github interface: https://github.blog/changelog/2022-03-24-ignore-commits-in-the-blame-view-beta/ |
.git-blame-ignore-revs
to ignore formatting PR from git blame
I already feel that it's a bit slower to track down changes so I would be for this, but I haven't used it before. What would be the downside if any? |
I never used it but I'm +1 on this. |
Rémi then proceeds to blame-ignore ALL the PRs he ever authored... 😜 |
See this comment: #3701 (comment) Also keep this issue opened until most of the reformatting is not over |
Related to #3701 (comment) git blame --ignore-revs-file .git-blame-ignore-revs nilearn/image/resampling.py copy paste of a comment from #3755 Still shows content from 3651 event though it is supposed to be ignored:
More annoyingly it is also still the case for: git blame --ignore-rev 44933309 nilearn/image/resampling.py |
We use one of these in Clinica. |
Thanks. |
I'm also unsure of how to make it work :/ If I get a chance I'll look into it some more |
Is there an existing issue for this?
Describe your proposed enhancement in detail.
Came across while browsing the black documentation:
https://black.readthedocs.io/en/stable/guides/introducing_black_to_your_project.html#avoiding-ruining-git-blame
One problem with all the reformating PRs is that they make reduce the usefulness (or at least add more friction) to the use of git blame to trace change was introduced when: black may end up touching many if not most lines in the code base and git blame may invariably point to one of those reformatting PRs when we use it, even though it very unlikely that a behavioral change came from them.
Using a
.git-blame-ignore-revs
could allow to "skip" to PR during a git blame call.Benefits to the change
Ideally this should facilitate the tracking down of changes in the code base by ignoring changes that pure reformatting and do not entail functional change.
The text was updated successfully, but these errors were encountered: