docs: Clarify PR guidelines w/re documentation

6 years ago · f4a230b627
parent bb68abe784
commit f4a230b627
1 changed files with 1 additions and 0 deletions
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@ -220,6 +220,7 @@ In general, all pull requests must:
  - 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.
+  - Change relevant comments and documentation when behaviour of code changes.

 Patches that change Bitcoin consensus rules are considerably more involved than
 normal because they affect the entire ecosystem and so must be preceded by