clang-format-action
clang-format-action copied to clipboard
jidicula
GitHub Action for clang-format checking
LLVM 18 is released now and it would be nice to have support for `clang-format-18`. It's currently available on [Ubuntu noble](https://packages.ubuntu.com/search?suite=all§ion=all&arch=any&keywords=clang-format-18&searchon=names).
We found in https://github.com/jidicula/clang-format-action/issues/198 and https://github.com/llvm/llvm-project/issues/93034 that LLVM occasionally introduces breaking changes in `clang-format` in patch (and presumably minor) version releases. Because this action just uses the latest version of...
We are using `clang-format` 18 via LLVM `18.1.5` but after formatting locally the files that the CI complains about in its checks, no changes are applied. Is there something we're...
See title. This allows any file with valid clang format contents to be specified as the filepath. In my organization this allows a submodule common across multiple C repositories to...
LLVM's official APT repository (https://apt.llvm.org) currently provides clang-format `17.0.6`, `18.1.8` and `19.1.0-rc4`.
Hey there, You've done a fantastic job providing all possible `clang-format` versions. However, at the moment the action insists on running `clang-format` itself. It would be very nice if you...
Hey! Thanks for this action. It's a convention across GitHub Actions to add a moving `v4` tag that always points to the latest release e.g. v4.11.3. Thanks in advance:)
Title says it all. Don't ask why we have folders named like that, and no, we physically cannot change the names =)
New file extensions included by default are: .ixx .cppm .ccm .c++m .cxxm
