aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSjors Provoost <[email protected]>2017-11-20 13:47:01 +0100
committerSjors Provoost <[email protected]>2017-11-20 13:47:01 +0100
commitfe27a72362ea8a165fd4648ee322541254d71228 (patch)
tree21dcbd638e6d831e3129467d70c3a783bd7571fc
parentMerge #11698: [Docs] [Qt] RPC-Console nested commands documentation (diff)
downloaddiscoin-fe27a72362ea8a165fd4648ee322541254d71228.tar.xz
discoin-fe27a72362ea8a165fd4648ee322541254d71228.zip
[docs] links to code style guides
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9f95d3f81..8381bd244 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -186,7 +186,7 @@ In general, all pull requests must:
the project (for example refactoring for modularisation);
- Be well peer reviewed;
- Have unit tests and functional tests where appropriate;
- - Follow code style guidelines;
+ - Follow code style guidelines ([C++](doc/developer-notes.md), [functional tests](test/functional/README.md));
- Not break the existing test suite;
- Where bugs are fixed, where possible, there should be unit tests
demonstrating the bug and also proving the fix. This helps prevent regression.