Add coverage baseline commit to git-blame-ignore #1613
Merged
Conversation
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
Adds commit 89e9c43 to .git-blame-ignore-revs to exclude the large-scale addition of # pragma: no cover comments from git blame output. This commit established a 100% code coverage baseline by adding pragma comments throughout the codebase. While important for coverage tracking, these annotations are noise in git blame and should be ignored to show the original authors of substantive code changes. Github-Issue: #1553
felixweinberger
approved these changes
Nov 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 commit 89e9c43 from PR #1553 to
.git-blame-ignore-revsto exclude the large-scale addition of# pragma: no covercomments from git blame output.Motivation and Context
PR #1553 established a 100% code coverage baseline by adding pragma comments throughout the codebase. While these annotations are valuable for coverage tracking, they add noise to git blame output by attributing lines to a formatting commit rather than showing the original authors of the substantive code.
Adding this commit to
.git-blame-ignore-revsensures thatgit blame(when configured to use the file) will skip over these pragma additions and show the actual authors of the underlying code logic.How Has This Been Tested?
This is a documentation/tooling change that affects git blame output only. The change can be verified by:
git blame --ignore-revs-file .git-blame-ignore-revs <file>on files modified in 89e9c43git config blame.ignoreRevsFile .git-blame-ignore-revsBreaking Changes
None.
Types of changes
Checklist
Additional context
This follows the same pattern as the existing entry for commit 5439619 (120 line-length formatting). Developers can configure git to automatically use this file with: