You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
Reporter: Ben Kietzman / @bkietz
Assignee: Kouhei Sutou / @kou
Related issues:
Note: This issue was originally created as ARROW-13664. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: