Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Add PR description to merge commit in github-merge.py #10786
+2
−0
Conversation
|
ACK
…
|
| @@ -175,6 +175,7 @@ def main(): | ||
| if info is None: | ||
| exit(1) | ||
| title = info['title'].strip() | ||
| + body = ' ' + info['body'].replace('\n', '\n ') |
promag
Jul 10, 2017
Contributor
I think here should be body = info['body'].strip() like the above. And the body indentation should be below.
|
ACK 475c08c. For the record, after this, the PR description must be part of the review process. Don't forget that there can be typos, markdown, links for temporary resources, etc that will be written in stone. Maybe for future improvement is to print the body and prompt for confirmation. |
|
Great idea. |
jonasschnelli
added the
Scripts and tools
label
Jul 11, 2017
|
Concept ACK |
laanwj
merged commit 475c08c
into
bitcoin:master
Jul 11, 2017
1 check passed
continuous-integration/travis-ci/pr
The Travis CI build passed
Details
laanwj
added a commit
that referenced
this pull request
Jul 11, 2017
|
|
laanwj |
ca4c545
|
|
I guess we are fine with HTML code in the PR description (=> goes then into git commit message)? |
ryanofsky
referenced
this pull request
Jul 12, 2017
Merged
[wallet] [tests] Add listwallets RPC, include wallet name in `getwalletinfo` and add multiwallet test #10604
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
sipa commentedJul 10, 2017
There is often some context given in PR descriptions that is missing from commits, and it may be worthwhile to retain that information in our history in git. This PR adds that information to the merge commit when created through
github-merge.py.We should also encourage people to provide as much information as possible in the PR commits themselves, but I believe that is an orthogonal issue. Individual commits don't need to have a description of the overall goal of a PR.