zhengruifeng opened a new pull request, #56923: URL: https://github.com/apache/spark/pull/56923
### What changes were proposed in this pull request? Follow-up to #56917 (SPARK-57795), which added a merge summary comment posted by `merge_spark_pr.py`. This PR refines the format of that comment: 1. Rename the header from `**Merge summary** (posted by `merge_spark_pr.py`):` to `**Merge Summary:**`. 2. Use the full commit SHA in the commit links (previously truncated to 8 characters). The `[:8]` truncation is dropped in `merge_pr` and `_do_cherry_pick`, with `.strip()` added since `run_cmd` does not strip the trailing newline. 3. Move the `merge_spark_pr.py` attribution to a trailing italic line: `*Posted by `merge_spark_pr.py`*`. Example rendered comment: > **Merge Summary:** > - merged into master https://github.com/apache/spark/commit/<full-sha> > - merged into branch-4.x https://github.com/apache/spark/commit/<full-sha> > > *Posted by `merge_spark_pr.py`* ### Why are the changes needed? A cleaner, more readable merge summary comment. Full SHAs are unambiguous and link-stable, and moving the tool attribution to the end keeps the summary itself front and center. ### Does this PR introduce _any_ user-facing change? No. This only affects the developer merge tooling. ### How was this patch tested? Manually verified the generated comment body and confirmed the full SHA is carried through. Existing lint (`ruff`) passes. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (model: 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]
