[feat] clang-tidy to output auditable information (per-file enabled/disabled checks)

[elupus]

When auditing a software release, it would be good to be able to see a log file from clang-tidy with actual enabled checks (per-file) as well as possible suppressed check inlined in source.

It is possible to run clang-tidy with --list-checks or --dump-config as a separate invocation. But having this type of output possible aughmented with "in-file" suppressions would be very usefull.

Also listing disabled checks would be useful.

[llvmbot]

@llvm/issue-subscribers-clang-tidy

Author: Joakim Plate (elupus)

When auditing a software release, it would be good to be able to see a log file from clang-tidy with actual enabled checks (per-file) as well as possible suppressed check inlined in source.

It is possible to run clang-tidy with --list-checks or --dump-config as a separate invocation. But having this type of output possible aughmented with "in-file" suppressions would be very usefull.

Also listing disabled checks would be useful.

[EugeneZelenko]

It'll be good idea to enhance run-clang-tidy.py in same way to complete code base audit.

It makes sense to dump only difference with main (in root directory) config file to simplify audit.

[5chmidti]

We could extend the --fixes output to include this information, then you'd have all diagnostics and this additional information in one place.

[elupus]

Yes i looked quickly at fixes. It almost seem to output what is needed. But it does not really end up fixes anymore if it output all files with empty fixes data? Still it's not a bad route.