This is an automated email from the ASF dual-hosted git repository.
gaogaotiantian 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 b53f3d04ed9d [SPARK-59913][INFRA] Point PR component-tag guidance in
AGENTS.md to the merge_spark_pr.py registry
b53f3d04ed9d is described below
commit b53f3d04ed9d54853a9ad320cde651e30ffa6d16
Author: Tian Gao <[email protected]>
AuthorDate: Mon Oct 5 16:16:55 2026 -0700
[SPARK-59913][INFRA] Point PR component-tag guidance in AGENTS.md to the
merge_spark_pr.py registry
### What changes were proposed in this pull request?
This updates the "Pull Request Workflow" section of `AGENTS.md` (aliased as
`CLAUDE.md`). The section previously described the PR-title component tag as
"derived from the JIRA component name: take the last word and uppercase it".
That rule is incorrect for many components -- for example `Documentation` maps
to `[DOC]` (not `[DOCUMENTATION]`), `Pandas API on Spark` maps to `[PS]`, and
`DStreams` maps to `[STREAMING]` -- and it ignores the accepted aliases.
The change points to the `COMPONENTS` registry in `dev/merge_spark_pr.py`
as the source of truth for the PR-title-tag to JIRA-component mapping, and
keeps a few illustrative examples.
### Why are the changes needed?
The documented heuristic produces wrong component tags for several JIRA
components. The `COMPONENTS` registry in `dev/merge_spark_pr.py` already
defines the canonical mapping and aliases, so the guidance should reference it
rather than restate an inaccurate rule.
### Does this PR introduce _any_ user-facing change?
No.
### How was this patch tested?
Documentation-only change; no tests. Verified the referenced `COMPONENTS`
registry and example mappings against `dev/merge_spark_pr.py`.
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.8)
Closes #59174 from gaogaotiantian/SPARK-claude-md-component.
Authored-by: Tian Gao <[email protected]>
Signed-off-by: Tian Gao <[email protected]>
---
AGENTS.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/AGENTS.md b/AGENTS.md
index 7331db3a4348..499b57ffcd42 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -205,7 +205,7 @@ It lists `master` and the latest major's release branches
the commit reached (e.
## Pull Request Workflow
-PR title format is `[SPARK-xxxx][COMPONENT] Title`. Draft, WIP, MINOR, and
TRIVIAL PRs may omit the JIRA ID. The component tag is derived from the JIRA
component name: take the last word and uppercase it (e.g. `Project Infra` →
`[INFRA]`, `Spark Core` → `[CORE]`, `Structured Streaming` → `[STREAMING]`,
`SQL` → `[SQL]`).
+PR title format is `[SPARK-xxxx][COMPONENT] Title`. Draft, WIP, MINOR, and
TRIVIAL PRs may omit the JIRA ID. The component tag comes from the `COMPONENTS`
registry in `dev/merge_spark_pr.py`, the source of truth: each entry pairs a
PR-title tag with its canonical JIRA component name and accepted aliases (e.g.
`Documentation` → `[DOC]`, `Pandas API on Spark` → `[PS]`, `SQL` → `[SQL]`).
Read that registry to pick the right tag.
Use `[FOLLOWUP]` only for small PRs that directly modify or correct unreleased
earlier PRs. For separately planned work, non-trivial changes, or work outside
the earlier JIRA's scope, create a separate JIRA ticket for each PR and use the
normal title format without `[FOLLOWUP]`.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
