Add '.git-blame-ignore-revs' to the project

[Mamaduka]

Description

PR adds .git-blame-ignore-revs to the project to improve git archeology.

You can read more about the ignore-rev in the following articles:

• https://akrabat.com/ignoring-revisions-with-git-blame/
• https://michaelheap.com/git-ignore-rev/

How has this been tested?

Test using the command below and it should ignore 4857ad5 commit.

git blame --ignore-revs-file .git-blame-ignore-revs -L 66,73 packages/api-fetch/src/middlewares/media-upload.js

Types of changes

DX

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR (please manually search all *.native.js files for terms that need renaming or removal).
• I've updated related schemas if appropriate. <!-- Reference: https://github.com/WordPress/gutenberg/tree/trunk/schemas ->

[Mamaduka]

If you are using GitLens extensions for VS Code, you can add the following settings:

"gitlens.advanced.blame.customArguments": ["--ignore-revs-file", ".git-blame-ignore-revs"],

[gziolo]

Is it something that GitHub supports as well or it's only helpful when you run the command?

[Mamaduka]

The feature isn't supported on Github yet - community/community#5033.

[gziolo]

The feature isn't supported on Github yet - github/feedback#5033.

Awesome, I commented there community/community#5033 (comment).

[oandregal]

Can this be problematic if one of the ignored revisions actually introduced a small bug? Think of unintentionally removing something, etc.

[Mamaduka]

@oandregal, I don't think so. You can still run git blame without --ignore-revs.

[gziolo]

How about we also include a section in the documentation explaining how to use this file (and maybe also a link in the file to the section). We could put it to the existing document:

https://github.com/WordPress/gutenberg/blob/trunk/docs/contributors/code/git-workflow.md

[noisysocks]

Didn't know about this 🙂 that's really cool.

[Mamaduka]

Sorry, I got stuck with documentation.

@gziolo, do you think this should be in a new section? Maybe "Advanced" or "Miscellaneous"?

P.S. I had some trouble doing git bisect on the project. It would be nice to include tips for doing it in the docs.

[gziolo]

do you think this should be in a new section? Maybe "Advanced" or "Miscellaneous"?

Sounds good, you just pick one 👍🏻

[Mamaduka]

@gziolo added a section in docs.

[gziolo]

Looks great, let’s land it ❤️