diff options
| author | Dave Houlton <daveh@lunarg.com> | 2018-02-06 17:49:16 -0700 |
|---|---|---|
| committer | Dave Houlton <daveh@lunarg.com> | 2018-02-16 09:31:58 -0700 |
| commit | 6ecf456fdf8132a38d8b599e7cf2756a7c09dddf (patch) | |
| tree | d23cb7414979c168f41119ec2acdcee61063b3ca | |
| parent | e714ff2b13ee9064b74123841ed6c6470e7df550 (diff) | |
| download | usermoji-6ecf456fdf8132a38d8b599e7cf2756a7c09dddf.tar.xz | |
tests: clang-format only
No code changes, just full clang-format.
Change-Id: I096d1b5509897bd642545e3369ccd83ca2849441
| -rw-r--r-- | CONTRIBUTING.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index dbc09253..2417cd4d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -57,6 +57,9 @@ a good reason is "This violates the style guide, but it improves type safety." * Run **clang-format** on your changes to maintain consistent formatting * There are `.clang-format files` present in the repository to define clang-format settings which are found and used automatically by clang-format. + * **clang-format** binaries are available from the LLVM orginization, here: https://clang.llvm.org/. Our CI system (Travis-CI) + currently uses clang-format version 5.0.0 to check that the lines of code you have changed are formatted properly. It is + recommended that you use the same version to format your code prior to submission. * A sample git workflow may look like: > # Make changes to the source. |