diff options
| author | Sjors Provoost <sjors@sprovoost.nl> | 2017-11-20 13:47:01 +0100 |
|---|---|---|
| committer | Sjors Provoost <sjors@sprovoost.nl> | 2017-11-20 13:47:01 +0100 |
| commit | fe27a72362ea8a165fd4648ee322541254d71228 (patch) | |
| tree | 21dcbd638e6d831e3129467d70c3a783bd7571fc | |
| parent | 7293d064133aeafd9f0ae0bdbb2ed74a44d91ecc (diff) | |
[docs] links to code style guides
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9f95d3f818..8381bd2448 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. |