uros-b opened a new pull request, #57848:
URL: https://github.com/apache/spark/pull/57848

   ### 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:
   
   ```diff
   -    Component("EXAMPLE", ("EXAMPLES",), jira_name="Examples"),
   +    Component("EXAMPLES", ("EXAMPLE",), primary=True, jira_name="Examples"),
   ```
   
   `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
   


-- 
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]

Reply via email to