Skip to content

Add .git-blame-ignore-revs to ignore linting and formatting commits #9422

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

Open
wants to merge 1 commit into
base: v2
Choose a base branch
from

Conversation

kdaily
Copy link
Member

@kdaily kdaily commented Apr 3, 2025

Issue #, if available:

Description of changes:

Ignore the commits related to linting and formatting when doing a git blame. This takes affect in GitHub and can be used in code editors as well. Note that if a previous commit cannot be identified on a line, git blame may still show changes from commits in this ignore file.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Ignore the commits related to linting and formatting.
@kdaily kdaily requested a review from aemous April 3, 2025 22:56
# PR 9374
d745ec22a88511414fb4a56292552a4dd2f9a5fb

# PR 9373
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like this PR was a squash + merge. The squashed commit that got merged into v2 was 6f5207d707e824f968f307395188d08a0de8344f. Neither of these 2 commits were actually merged to v2 due to being squashed.

Do you mind (1) replacing these 2 commit SHAs with the squashed one and (2) verify that all the other squashed+merged PRs in this file use the squashed commit SHA rather than the individual commits?

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.

None yet

2 participants