Skip to content
This repository was archived by the owner on Mar 14, 2023. It is now read-only.

Commit 04c0355

Browse files
Merge pull request #327 from jhg/issue_900_of_rustc_dev_guide
Remove recommendation about how to add changes to the pull request
2 parents 2d25939 + 5e764f2 commit 04c0355

File tree

3 files changed

+2
-6
lines changed

3 files changed

+2
-6
lines changed

highfive/newpr.py

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,6 @@
2222
welcome_without_reviewer = "@nrc (NB. this repo may be misconfigured)"
2323
raw_welcome = """Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from %s soon.
2424
25-
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
26-
2725
Please see [the contribution instructions](%s) for more information.
2826
"""
2927

highfive/tests/test_integration_tests.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ def test_new_pr_non_contributor(self):
103103
(
104104
'POST', newpr.post_comment_url % ('rust-lang', 'rust', '7'),
105105
{
106-
'body': "Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nrc (or someone else) soon.\n\nIf any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.\n\nPlease see [the contribution instructions](https://rustc-dev-guide.rust-lang.org/contributing.html) for more information.\n"}
106+
'body': "Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nrc (or someone else) soon.\n\nPlease see [the contribution instructions](https://rustc-dev-guide.rust-lang.org/contributing.html) for more information.\n"}
107107
),
108108
{'body': {}},
109109
),
@@ -145,7 +145,7 @@ def test_new_pr_empty_body(self):
145145
(
146146
'POST', newpr.post_comment_url % ('rust-lang', 'rust', '7'),
147147
{
148-
'body': "Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nrc (or someone else) soon.\n\nIf any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.\n\nPlease see [the contribution instructions](https://rustc-dev-guide.rust-lang.org/contributing.html) for more information.\n"}
148+
'body': "Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nrc (or someone else) soon.\n\nPlease see [the contribution instructions](https://rustc-dev-guide.rust-lang.org/contributing.html) for more information.\n"}
149149
),
150150
{'body': {}},
151151
),

highfive/tests/test_newpr.py

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -112,8 +112,6 @@ class TestNewPRGeneral(TestNewPR):
112112
def test_welcome_msg(self):
113113
base_msg = """Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from %s soon.
114114
115-
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
116-
117115
Please see [the contribution instructions](%s) for more information.
118116
"""
119117

0 commit comments

Comments
 (0)