.git-blame-ignore-revs: Ignore black format change #25609
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.
Suggestion cannot be applied right now. Please check back later.
This reduces commit noise in Tools/ros2 by ignoring our mass-format commit when we switched to black. I'd like to propose this as a way to start ignoring commits in ArduPilot that are format-only.
For more info on how this feature works, see here:
https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view
This approach is used on other major repos with >1M Lines of Code like GDAL:
https://gdal.org/development/rfc/rfc69_cplusplus_formatting.html
This strategy can be used in the future to ignore things like
Using automated formatting reduces developer time, so that people like Randy do not need to spend cognitive load nitpicking style and instead focus on logic errors and other things that affect behavior or maintainability.
Yes, refactor and automated tools need to be applied carefully because it makes backporting difficult. This PR in no way changes that existing process, but it does reduce the developer effect of mass-changes on the git blame.