diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2022-02-23 19:20:49 +0100 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2022-02-24 13:47:47 +0100 |
| commit | fa694f61ab21cb973843e5234a6aeacd4a957e05 (patch) | |
| tree | 50ac6dd4373a4d43e0fb964c546aa0926b3ea97a | |
| parent | fa0819eea380047c9d7404895d3e4e8ea37930bb (diff) | |
| download | bitcoin-fa694f61ab21cb973843e5234a6aeacd4a957e05.tar.xz | |
doc: Explain that feedback needs to be addressed
| -rw-r--r-- | CONTRIBUTING.md | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 55f599fdd2..254e610393 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -189,7 +189,12 @@ in the body of the pull request to indicate tasks are pending. At this stage, one should expect comments and review from other contributors. You can add more commits to your pull request by committing them locally and pushing -to your fork until you have satisfied all feedback. +to your fork. + +You are expected to reply to any review comments before your pull request is +merged. You may update the code or reject the feedback if you do not agree with +it, but you should express so in a reply. If there is outstanding feedback and +you are not actively working on it, your pull request may be closed. Please refer to the [peer review](#peer-review) section below for more details. |