zhengruifeng opened a new pull request, #56026:
URL: https://github.com/apache/spark/pull/56026
### What changes were proposed in this pull request?
Add a check in `dev/merge_spark_pr.py` that prompts the committer for one or
more `[COMPONENT]` tags when the PR title lacks them, then inserts the tags
into the title after the `[SPARK-XXX]` ref(s).
The prompt lists common Spark components with brief descriptions:
```
PR title is missing the [COMPONENT] tag.
Common components:
[CORE] - Spark Core
[SQL] - Spark SQL
[SS] - Structured Streaming
[STREAMING] - DStream API
[CONNECT] - Spark Connect
[PYTHON] - PySpark
[PS] - pandas API on Spark
[ML] - Spark ML (DataFrame-based)
[MLLIB] - MLlib (RDD-based)
[R] - SparkR
[GRAPHX] - GraphX
[UI] - Spark Web UI
[K8S] - Kubernetes
[YARN] - Hadoop YARN
[BUILD] - build system
[INFRA] - project infrastructure
[DOCS] - documentation changes
[TESTS] - test-only changes
Current title: [SPARK-56853] Improve PATH Tests
Enter comma-separated component(s) to insert into the title (e.g. CORE,SQL):
```
Status markers (`[MINOR]`, `[FOLLOWUP]`, `[FOLLOW-UP]`, `[TRIVIAL]`) do not
satisfy the component requirement. Revert PRs, which reuse the original
commit's title verbatim, are skipped. `[WIP]` is intentionally not on the
marker list — a WIP PR should be aborted at the earlier WIP warning, not merged.
### Why are the changes needed?
Some PRs are merged without a `[COMPONENT]` tag in the title (e.g.
apache/spark#55866 was merged as `[SPARK-56853] Improve PATH Tests`). This
loses module attribution in the changelog and breaks the convention
`[SPARK-XXXXX][COMPONENT] Title` that Spark uses.
### Does this PR introduce _any_ user-facing change?
No. The change only affects the committer-facing interactive merge tool.
### How was this patch tested?
Added doctests for `title_missing_component` and
`insert_components_into_title`. All doctests pass via `python3 -m doctest
dev/merge_spark_pr.py`.
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code
--
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]
