-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Document when and how to .git-blame-ignore-revs #130737
Copy link
Copy link
Closed
rust-lang/rustc-dev-guide
#2072Labels
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsArea: Documentation for any part of the project, including the compiler, standard library, and toolsT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsArea: Documentation for any part of the project, including the compiler, standard library, and toolsT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Originally posted by @jieyouxu in #130736 (comment)
Some large reformatting or refactoring PRs that don't otherwise contain functional changes might be good candidates for
.git-blame-ignore-rev(but want to be conservative about which commits qualify so we don't miss out on commits that would benefit from being present in blame)