Thank you for your commenst :) but let me ask a question: Why do you consider them mutable? They are related into a commit and they are stored into an specific ref (it is not the default for Git notes). Git notes are also used to store static code analysis results.
The tool could generate the report as a file, sure. But The problem is that you will need a service to retrieve that file and compare - and then it becomes a non generic solution.
Indeed, my question is what do you want to do with that file? It can generate it, but nobody will take benefit of it, right?
However, take in mind that the report is stored inside the Git repository as a note (it is invisible - and how other tools like Gerrit work) to avoid an external service.
It is a respectable point of view, but I think that automatize some boring tasks to correct inside the code is a good idea because let you work on other more interesting tasks.
In fact, most of us use some automatic ways to correct and enrich code with IDEs. Is it also incorrect? In fact, what we are trying to solve are the following situations:
a) In a context where there are a lot of developers and you have worked hard into improve the code style and someone else pushed code that again violates your "implicit" code style. Do you need to correct these bad practices over and over again?
b) There are some boring tasks that punctually appear like "refactoring" when deprecated methods appear or developers need to upgrade one external library version (eg. one critical bug appears).
Yes, but in contrast with removing unused private methods, currently there is no walkmod plugin that do this yet. We are working on adding more plugins.
The tool could generate the report as a file, sure. But The problem is that you will need a service to retrieve that file and compare - and then it becomes a non generic solution.
Indeed, my question is what do you want to do with that file? It can generate it, but nobody will take benefit of it, right?