Skip to content

Conversation

@Lestropie
Copy link
Member

Closes #2590.

Some notes:

  1. This does not influence reporting of contribution statistics in any way; it just prevents certain commits from appearing in the individual lines of git blame.
  2. It does not prevent commits from appearing in the history of commits influencing any given file on GitHub.
  3. As noted in Use .git-blame-ignore-revs to ignore mass copyright commit and other formatting commits #2590, this should be utilised in Port from C++11 to C++17 #2585 to prevent the exploitation of nested namespaces from swamping git blame.

@Lestropie Lestropie requested a review from a team March 1, 2023 02:03
@Lestropie Lestropie self-assigned this Mar 1, 2023
Copy link
Member

@jdtournier jdtournier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fairly innocuous, happy to merge.

@jdtournier jdtournier added this pull request to the merge queue Mar 3, 2023
Merged via the queue into master with commit 260d9c9 Mar 3, 2023
@jdtournier jdtournier deleted the git_blame_ignore_revs branch March 3, 2023 10:03
@Lestropie Lestropie restored the git_blame_ignore_revs branch August 26, 2025 08:11
@Lestropie Lestropie deleted the git_blame_ignore_revs branch August 27, 2025 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use .git-blame-ignore-revs to ignore mass copyright commit and other formatting commits

3 participants