This is an automated email from the ASF dual-hosted git repository.
cloud-fan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/master by this push:
new f57294052cef [SPARK-58638][INFRA] Recognize Examples as a primary
component tag in the merge script
f57294052cef is described below
commit f57294052cefb20f32b9b921ccc6e2eb10d93024
Author: Uros Bojanic <[email protected]>
AuthorDate: Sat Aug 8 01:02:04 2026 +0800
[SPARK-58638][INFRA] Recognize Examples as a primary component tag in the
merge script
### What changes were proposed in this pull request?
This PR marks the `EXAMPLES` component as `primary` in the `COMPONENTS`
registry of `dev/merge_spark_pr.py`, and makes the plural spelling the
canonical tag.
`EXAMPLE` remains an accepted alias, so both `[EXAMPLES]` and `[EXAMPLE]`
continue to be recognized; the canonical form used when the script rewrites a
title is now the plural `[EXAMPLES]`.
### Why are the changes needed?
Since SPARK-56979, the merge script requires every PR title to carry at
least one **primary** component tag. `EXAMPLES` maps to the JIRA component
"Examples" and names a real top-level build module (`examples/` in `pom.xml`),
but it was not marked `primary`. As a result, a PR titled e.g.
`[SPARK-XXXXX][EXAMPLES] ...` is rejected at merge time with:
```
PR title is missing a primary [COMPONENT] tag.
Primary components (one of these is required):
...
Enter comma-separated component(s) to insert into the title (e.g. CORE,SQL):
```
This forces the committer to bolt on a possibly unrelated primary tag,
which produces worse changelog attribution than `[EXAMPLES]` alone for a change
that lives entirely in the examples module. The plural `[EXAMPLES]` is also the
more common historical spelling (92 vs 38 for the singular) and the form
implied by deriving the tag from the JIRA component name ("Examples"), so it is
made the canonical spelling while the singular stays as an alias.
### Does this PR introduce _any_ user-facing change?
No. This only affects the committer-facing interactive merge tool
(`dev/merge_spark_pr.py`).
### How was this patch tested?
- Existing doctests pass:
```
python3 -m doctest dev/merge_spark_pr.py
```
- Manually verified against the registry and the merge-time gate.
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code
Closes #57848 from uros-b/SPARK-examples-primary.
Authored-by: Uros Bojanic <[email protected]>
Signed-off-by: Wenchen Fan <[email protected]>
---
dev/merge_spark_pr.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev/merge_spark_pr.py b/dev/merge_spark_pr.py
index 1e8b13d70e74..f0c91c77f427 100755
--- a/dev/merge_spark_pr.py
+++ b/dev/merge_spark_pr.py
@@ -1299,7 +1299,7 @@ COMPONENTS = (
Component("DOC", ("DOCS", "DOCUMENTATION"), primary=True,
jira_name="Documentation"),
Component("DOCKER", primary=True, jira_name="Spark Docker"),
Component("EC2", jira_name="EC2"),
- Component("EXAMPLE", ("EXAMPLES",), jira_name="Examples"),
+ Component("EXAMPLES", ("EXAMPLE",), primary=True, jira_name="Examples"),
Component("GRAPHX", primary=True, jira_name="GraphX"),
Component("INFRA", ("PROJECT_INFRA",), primary=True, jira_name="Project
Infra"),
Component("IO", jira_name="Input/Output"),
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
