This is an automated email from the ASF dual-hosted git repository.
kou pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/arrow.git
The following commit(s) were added to refs/heads/master by this push:
new dc11d4394a ARROW-16786: [Docs] Update "closed without merge" in pull
request note (#13341)
dc11d4394a is described below
commit dc11d4394a51850e0039f9f30940a6a81d3385b7
Author: Alenka Frim <[email protected]>
AuthorDate: Thu Jun 9 01:27:09 2022 +0200
ARROW-16786: [Docs] Update "closed without merge" in pull request note
(#13341)
Authored-by: Alenka Frim <[email protected]>
Signed-off-by: Sutou Kouhei <[email protected]>
---
docs/source/developers/overview.rst | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/docs/source/developers/overview.rst
b/docs/source/developers/overview.rst
index d3f97173e3..3c580afba7 100644
--- a/docs/source/developers/overview.rst
+++ b/docs/source/developers/overview.rst
@@ -135,12 +135,10 @@ will merge the pull request. This is done with a
history to identify where changes were introduced, and helps us be able to
cherry-pick individual patches onto a maintenance branch.
- A side effect of this way of merging is that your pull request will appear
- in the GitHub interface to have been "closed without merge".
- Do not be alarmed: if you look at the bottom, you will see a message that
- says ``@user closed this in $COMMIT``. In the commit message of that commit,
- the merge tool adds the pull request description, a link back to the pull
- request, and attribution to the contributor and any co-authors.
+ Your pull request will appear in the GitHub interface to have been "merged".
+ In the commit message of that commit, the merge tool adds the pull request
+ description, a link back to the pull request, and attribution to the
contributor
+ and any co-authors.
.. Section on Experimental repositories:
