[JENKINS-55719] Allow to configure the git blame command to suppress whitespace changes

Sometimes the git blame command does not find the right person as there were whitespace changes (e.g. due to formatting) or code was moved. In this case it is possible to use "git blame -w -M" to suppress commits that only contain those changes and get better results

I suggest to make the used git blame command configurable.

 

There are two possible places:

1. in the global configuration.


2. in the warnings step itself.

As the implementation in the global settings is much easier I guess it could be done there. The only reason not to have it there would be to have different settings for different parsers (e.g. if you have one parser in the job that would be sensitive to whitespace changes).

---
Originally reported by tstein, imported from: Allow to configure the git blame command to suppress whitespace changes

• status: Open
  
• priority: Minor
  
• component(s): git-forensics-plugin
  
• label(s): hacktoberfest, help-wanted, newbie-friendly
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 3
  
• imported: 20260107-220949
  

Raw content of original issue

Sometimes the git blame command does not find the right person as there were whitespace changes (e.g. due to formatting) or code was moved. In this case it is possible to use "git blame -w -M" to suppress commits that only contain those changes and get better results


I suggest to make the used git blame command configurable.


 


There are two possible places:



	
in the global configuration.

	
in the warnings step itself.



As the implementation in the global settings is much easier I guess it could be done there. The only reason not to have it there would be to have different settings for different parsers (e.g. if you have one parser in the job that would be sensitive to whitespace changes).