szehon-ho opened a new pull request, #142: URL: https://github.com/apache/spark-docker/pull/142
### What changes were proposed in this pull request? After a successful push, `dev/merge_spark_docker_pr.py` posts a **Merge Summary** comment on the pull request with the target branch and resulting commit link. This ports the comment behavior from Spark's `dev/merge_spark_pr.py`, using the existing `GITHUB_OAUTH_KEY` for authentication. The script skips the comment when no token is configured and reports HTTP or connection errors while allowing the JIRA update to continue. ### Why are the changes needed? Record where the change landed directly on the pull request, so contributors can find the resulting commit after a squash merge. ### Does this PR introduce _any_ user-facing change? Committers who configure `GITHUB_OAUTH_KEY` now get an automatic merge summary comment on the pull request. ### How was this patch tested? - `PYTHONDONTWRITEBYTECODE=1 python3 -m doctest -v dev/merge_spark_docker_pr.py`: all 9 doctests passed. - Ran 6 focused checks with mocked Git, GitHub, and JIRA calls: comment formatting and authentication for master and a release branch; skipping without a token; posting after a successful push and before JIRA; avoiding comments after failed pushes; and continuing JIRA updates after missing tokens, HTTP errors, or connection errors. These checks were run locally without adding a new test harness to the repository. - `git diff --check` passed. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Codex (GPT-6) -- 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]
