[git-clang-format] Add --diffstat parameter

[roligugus]

Summary

[git-clang-format][PR46815] Add diffstat functionality

Adding a --diffstat parameter to git-clang-format that essentially uses git diff --stat, i.e. lists the files needing
formatting. This is useful for CI integration or manual usage where one wants to list the files not properly formatted.

I use it for the Suricata project's github action (CI) integration that verifies proper formatting of a pull request
according to project guidelines where it's very helpful to say which files are not properly formatted. I find the list
of files much more useful than e.g. showing the diff in this case using git-clang-format --diff.

An alternative would be to take an additional parameter to diff, e.g. git-clang-format --diff --stat

The goal is not to provide the whole git diff --stat=... parameter functionality, just plain git diff --stat.

[roligugus]

clang/tools/clang-format/git-clang-format

102

As mentioned in the description, an alternative would be to add a --stat parameter and hand that to print_diff(). E.g. user would call it then with git-clang-format --diff --stat.

Would result in less code duplication of print_diff() vs print_diffstat().

[aheejin]

This looks fine to me, but I haven't worked on this part of code myself, so probably others who have can provide better review.

[JakeMerdichAMD]

Reviving this since it looks perfectly fine to me (from my limited commit history in git-clang-format :P), is useful, and there's no good reason for it to be stalled.

I'll wait a day or two to see if there's any objections, then accept it.

[roligugus]

@JakeMerdichAMD, @MyDeveloperDay
Sorry to bother with a re-review. Did not know how to ask this.

Jake accepted this patch last August and it has been sitting in "ready to land" since then. I was assuming that it'll automatically make it into the main line after the acceptance. My bad, I should have read the policy and practices better.

Do you mind re-accepting and then committing this? I don't have any commit rights.

Sorry, I should have followed up way earlier. I was finally getting around to this and wanted to take our local patch out and was assuming this was in the latest clang, but it isn't.

[MyDeveloperDay]

@roligugus I can land this for you, please rebase the review then please add your name and email here so we can ensure you get the credit.

https://llvm.org/docs/DeveloperPolicy.html#commit-messages

[roligugus]

[git-clang-format] Rebase D84375 on latest main

[roligugus]

@MyDeveloperDay Thanks for the follow-up! I've rebased on latest main.

Out of curiosity, as I am trying to wrap my head around the llvm workflow: Could I arc land ... myself once you sign off with "ready to land" even if I don't have llvm commit rights? If so, please let me know and I'll do that.

Otherwise, I've set the author on my commit, but if you need to set it: git commit --amend --author="Roland Fischer <[e-mail]>"

Thanks a lot!

[MyDeveloperDay]

In D84375#3065785, @roligugus wrote:

@MyDeveloperDay Thanks for the follow-up! I've rebased on latest main.

Out of curiosity, as I am trying to wrap my head around the llvm workflow: Could I arc land ... myself once you sign off with "ready to land" even if I don't have llvm commit rights? If so, please let me know and I'll do that.

Otherwise, I've set the author on my commit, but if you need to set it: git commit --amend --author="Roland Fischer <[e-mail]>"

Thanks a lot!

I personally don't use arc so I can't answer that, you DO need commit rights though, and you are free to apply for those. (normally I think you need to do some small issues first), but its worth applying if you plan to continue to contribute

I can land this for you for now.

[MyDeveloperDay]

I just tested this an it seems to work

$ git clang-format --diffstat
 clang/lib/Format/Format.cpp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)