sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-25 12:02:48 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge #11729: [docs] links to code style guides

Browse Source 
fe27a7236 [docs] links to code style guides (Sjors Provoost)

Pull request description:

  I always have difficulty finding these, probably because they're not actually called "code style guideline".

Tree-SHA512: a2716c5e7e6778ce71b4451091e3899c0f9e04d07e95d1a0bdb07eb0319c083e3d9aa94bc2e33fc8546f82a1441e73c37218fdc7f228ee8273c7a87466958973
This commit is contained in:
MarcoFalke 2017-11-20 15:15:29 -05:00 committed by Pasta
parent f7f33091e1
commit 3d6713d651
No known key found for this signature in database
GPG Key ID: 52527BEDABE87984
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING.md
View File

@ -178,7 +178,7 @@ In general, all pull requests must:
the project (for example refactoring for modularisation); the project (for example refactoring for modularisation);
- Be well peer reviewed; - Be well peer reviewed;
- Have unit tests and functional tests where appropriate; - Have unit tests and functional tests where appropriate;
- Follow [code style guidelines](/doc/developer-notes.md); - Follow code style guidelines ([C++](doc/developer-notes.md), [functional tests](test/functional/README.md));
- Not break the existing test suite; - Not break the existing test suite;
- Where bugs are fixed, where possible, there should be unit tests - Where bugs are fixed, where possible, there should be unit tests
demonstrating the bug and also proving the fix. This helps prevent regression. demonstrating the bug and also proving the fix. This helps prevent regression.