You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Ben Kietzman (Jira)" <ji...@apache.org> on 2021/08/18 15:27:00 UTC

[jira] [Created] (ARROW-13664) [Developer] Append comments explaining merge process in merge_arrow_pr.py

Ben Kietzman created ARROW-13664:
------------------------------------

             Summary: [Developer] Append comments explaining merge process in merge_arrow_pr.py
                 Key: ARROW-13664
                 URL: https://issues.apache.org/jira/browse/ARROW-13664
             Project: Apache Arrow
          Issue Type: Improvement
          Components: Developer Tools
            Reporter: Ben Kietzman


dev/merge_arrow_pr.py is a nifty tool, but due to the way it avoids use of a GitHub-sanctioned merge it frequently confuses newcomers who see "closed" instead of "merged" PRs.

This could be ameliorated by automatically adding a comment to the PR directly after the "closed" event explaining that the PR is in fact merged and linking to an full breakdown of our alternative git flow.

Additionally for visibility in contexts where only the PR headline is visible it'd be useful to attach a "merged" label and/or place a [MERGED] tag in the title



--
This message was sent by Atlassian Jira
(v8.3.4#803005)