chore: record the Prettier reformat in .git-blame-ignore-revs - #198
Merged
Conversation
Follow-up to #192, which could not carry its own SHA: this repo squash-merges, so the commit did not exist until it landed on staging. It is c970bc9. Measured effect on the worst-hit files -- lines git blame credited to the formatter, before -> after: src/commands/team.js 55 of 188 -> 1 src/adapters/discord.js 40 of 591 -> 0 src/commands/doc.js 30 of 128 -> 1 src/web/public/app.js 23 of 304 -> 0 src/meeting/meetingSurface.js 22 of 259 -> 0 Nearly a third of team.js blamed on a formatting pass. Now it points at whoever wrote the line. GitHub applies this automatically in its blame view. Locally it is opt-in once per clone: git config blame.ignoreRevsFile .git-blame-ignore-revs
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
1 participant
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.
What this changes
Appends the real squash SHA to
.git-blame-ignore-revs.Why it's a separate PR
#192 couldn't carry its own SHA. This repo squash-merges, so the commit didn't exist until it landed on
staging— any SHA committed on the branch would have silently matched nothing. #192 shipped the file with aTODO; this closes it. The SHA isc970bc9.Measured effect
Lines
git blamecredited to the formatter, before → after, on the worst-hit files:src/commands/team.jssrc/adapters/discord.jssrc/commands/doc.jssrc/web/public/app.jssrc/meeting/meetingSurface.jsNearly a third of
team.jswas blaming a formatting pass. Now it points at whoever wrote the line — which is the whole reason to keep history readable in a repo where the author has usually graduated.How to verify
GitHub applies the file automatically in its blame view. Locally it's opt-in once per clone:
Zone
root.🤖 Generated with Claude Code