Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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
Attachments
Issue Links
- is superceded by
-
ARROW-16602 [Dev] Use GitHub API to merge pull request
- Resolved