aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Lobodzinski <mark@lunarg.com>2017-01-25 07:56:21 -0700
committerMark Lobodzinski <mark@lunarg.com>2017-01-25 07:56:21 -0700
commit47ee2d30e9878d0489cd9db71b473232be815414 (patch)
tree028c96f1424fcd0f728bdd3dc1f5c81939d6d425
parent755999c01090f47037443fbf8326356cb8ebc06c (diff)
downloadusermoji-47ee2d30e9878d0489cd9db71b473232be815414.tar.xz
docs: Update contributing doc
Change-Id: I3ead4ff33591c55312eab9b6a6b515d0453ab796
-rw-r--r--CONTRIBUTING.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 67bf2412..20c4f4f0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -46,6 +46,7 @@ later on this page.
#### **Coding Conventions and Formatting**
* Use the [Google style guide](https://google.github.io/styleguide/cppguide.html) for source code with the following two exceptions.
* The column limit is 132 (as opposed to the default value 80). The clang-format tool will handle this. See below.
+ * The indent is 4 spaces instead of the default 2 spaces. Again, the clang-format tool will handle this.
* If you can justify a reason for violating a rule in the guidelines, then you are free to do so. Be prepared to defend your decision during code review. This should be used responsibly. An example of a bad reason is “I don’t like that rule.” An example of a good reason is “This violates the style guide, but it improves type safety.”
* Run clang-format on your changes to maintain formatting.