chore: exclude trivial refactors from git blame
results
#12550
Merged
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.
See https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view
Ideally, all style-only-commits should be put on this list.
The "move to typescript" is not trivial by itself, but most of the
additions/deletions are style changes. So I think it's safe and more
reader-friendly to exclude it.
Blame view before the PR:
https://github.com/vuejs/vue/blame/v2.7.0-alpha.4/src/platforms/web/runtime/transition-util.ts
After the PR:
https://github.com/sodatea/vue/blame/chore-better-git-blame/src/platforms/web/runtime/transition-util.ts
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch for v2.x (or to a previous version branch), not themaster
branchfix #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: