
git clone git://git.z3bra.org/qmk.git
Log | Files | Refs | Submodules | LICENSE

commit dc5933aff7d948c1bb1e6199259509f20d170768
parent ae9439a3f984641b8bc4c1e0d5c5c1818e0b2e32
Author: James Churchill <pelrun@gmail.com>
Date:   Sun, 17 Feb 2019 17:31:47 +1000

Add clang-format section to contributing.md

docs/contributing.md | 12++++++++++++
1 file changed, 12 insertions(+), 0 deletions(-)

diff --git a/docs/contributing.md b/docs/contributing.md @@ -91,6 +91,18 @@ int foo(void) { } ``` +# Auto-formatting with clang-format + +[Clang-format](https://clang.llvm.org/docs/ClangFormat.html) is part of LLVM and can automatically format your code for you, because ain't nobody got time to do it manually. We supply a configuration file for it that applies most of the coding conventions listed above. It will only change whitespace and newlines, so you will still have to remember to include optional braces yourself. + +Use the [full LLVM installer](http://llvm.org/builds/) to get clang-format on Windows, or use `sudo apt install clang-format` on Ubuntu. + +If you run it from the command-line, pass `-style=file` as an option and it will automatically find the .clang-format configuration file in the QMK root directory. + +If you use VSCode, the standard C/C++ plugin supports clang-format, alternatively there is a [separate extension](https://marketplace.visualstudio.com/items?itemName=LLVMExtensions.ClangFormat) for it. + +Some things (like LAYOUT macros) are destroyed by clang-format, so either don't run it on those files, or wrap the sensitive code in `// clang-format off` and `// clang-format on`. + # General Guidelines We have a few different types of changes in QMK, each requiring a different level of rigor. We'd like you to keep the following guidelines in mind no matter what type of change you're making.