[jira] [Resolved] (ARROW-16786) [Docs] Update "closed without merge" in pull request note

["Kouhei Sutou (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARROW-16786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kouhei Sutou resolved ARROW-16786.
----------------------------------
    Fix Version/s: 9.0.0
       Resolution: Fixed

Issue resolved by pull request 13341
[https://github.com/apache/arrow/pull/13341]

> [Docs] Update "closed without merge" in pull request note
> ---------------------------------------------------------
>
>                 Key: ARROW-16786
>                 URL: https://issues.apache.org/jira/browse/ARROW-16786
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Kouhei Sutou
>            Assignee: Alenka Frim
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 9.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> https://arrow.apache.org/docs/developers/overview.html#pull-request-and-review
> {quote}
> 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.
> {quote}
> We have changed to use the "merge" feature of GitHub by ARROW-16602 to show "merged" mark not "closed without merge" mark on GitHub. We should update the note.
> [~alenkaf] Do you want to work on this?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)