zhengruifeng opened a new pull request, #56917: URL: https://github.com/apache/spark/pull/56917
### What changes were proposed in this pull request? After a PR is merged (and any cherry-picks are done), `dev/merge_spark_pr.py` now posts a single comment on the PR recording every branch the change landed on and a link to the resulting commit, e.g.: ``` MERGE_SPARK_PR: - merged into master https://github.com/apache/spark/commit/0e1101aa - merged into branch-4.x https://github.com/apache/spark/commit/964f8da1 - merged into branch-4.2 https://github.com/apache/spark/commit/9a6bd1ef ``` New helpers `comment_pr` (POST `issues/{pr}/comments`) and `post_merge_comment` build and post the comment. `_do_cherry_pick` now returns `(ref, hash)` and `cherry_pick` returns a list of such pairs so the exact backport commits can be listed. The comment is posted from both the normal merge path and the already-merged backport path, and is skipped when `GITHUB_OAUTH_KEY` is unset. ### Why are the changes needed? A merged PR shows up on GitHub as Closed, and the master merge commit is folded into the close event rather than a "referenced in commit" link, so it is not obvious from the PR page which branches actually received the change. An explicit comment makes the merge fully traceable from the PR. ### Does this PR introduce _any_ user-facing change? No. Committer tooling only. ### How was this patch tested? `python -m py_compile` and the module doctests pass. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (claude-opus-4-8) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
