Skip to content

Commit 942e275

Browse files
committed
Merge #16962: doc: Put PR template in comments
203a67d doc: Put PR template in comments (Wladimir J. van der Laan) Pull request description: This prevents the common annoyance of the text being included into PRs accidentally. ACKs for top commit: sdaftuar: utACK 203a67d fanquake: ACK 203a67d - I make an effort to remove it whenever I see it in a PR. Tree-SHA512: 3514d285488b7930d7f3d7f8823198d7325d8b7de57a6d8f13e559c0c23b30d58916b15782cbbdc347a375b418e9d0f7a5b99b34d26f3b957d7d5a03a3d83dfd
2 parents 6b9405e + 203a67d commit 942e275

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,14 @@
1+
<!--
2+
*** Please remove the following help text before submitting: ***
3+
14
Pull requests without a rationale and clear improvement may be closed
25
immediately.
6+
-->
37

8+
<!--
49
Please provide clear motivation for your patch and explain how it improves
510
Bitcoin Core user experience or Bitcoin Core developer experience
6-
significantly.
11+
significantly:
712
813
* Any test improvements or new tests that improve coverage are always welcome.
914
* All other changes should have accompanying unit tests (see `src/test/`) or
@@ -24,8 +29,11 @@ significantly.
2429
is often a subjective matter. Unless they are explicitly mentioned to be
2530
preferred in the [developer notes](/doc/developer-notes.md), stylistic code
2631
changes are usually rejected.
32+
-->
2733

34+
<!--
2835
Bitcoin Core has a thorough review process and even the most trivial change
2936
needs to pass a lot of eyes and requires non-zero or even substantial time
3037
effort to review. There is a huge lack of active reviewers on the project, so
3138
patches often sit for a long time.
39+
-->

0 commit comments

Comments
 (0)