diff options
| author | Carl Dong <accounts@carldong.me> | 2019-04-11 12:54:20 -0400 |
|---|---|---|
| committer | Carl Dong <accounts@carldong.me> | 2019-04-11 12:54:20 -0400 |
| commit | f4a230b627bf9ff53e14719609849ee05b022480 (patch) | |
| tree | ee68effa04cfaf6f8a5524a93b4700f7be585f4a | |
| parent | bb68abe784b9fd49bddf38105d142a31ef0f9e77 (diff) | |
| download | bitcoin-f4a230b627bf9ff53e14719609849ee05b022480.tar.xz | |
docs: Clarify PR guidelines w/re documentation
| -rw-r--r-- | CONTRIBUTING.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 007ebd7ccf..5df99adba8 100644 --- 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 |