This is an automated email from the ASF dual-hosted git repository.
zhengruifeng pushed a commit to branch branch-4.x
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/branch-4.x by this push:
new e12f6cc8c175 [MINOR][INFRA] Clarify JIRA reuse for follow-up PRs
e12f6cc8c175 is described below
commit e12f6cc8c1755d70e2563e0a500d62abfa202e36
Author: Ruifeng Zheng <[email protected]>
AuthorDate: Mon Aug 24 11:35:44 2026 +0800
[MINOR][INFRA] Clarify JIRA reuse for follow-up PRs
### What changes were proposed in this pull request?
Clarify the pull request workflow in `AGENTS.md`: follow-up PRs reuse the
JIRA ticket from the earlier PR and must not create a new ticket.
### Why are the changes needed?
This avoids duplicate JIRA tickets for work that is already tracked by an
existing issue.
### Does this PR introduce _any_ user-facing change?
No.
### How was this patch tested?
`git diff --check` passed. No runtime tests were run because this only
updates contributor instructions.
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Codex CLI 0.146.1
Closes #57818 from zhengruifeng/minor/clarify-followup-pr-jira.
Authored-by: Ruifeng Zheng <[email protected]>
Signed-off-by: Ruifeng Zheng <[email protected]>
(cherry picked from commit e6a7a52b44d8bbf8100bb960ad81153862b9ccc9)
Signed-off-by: Ruifeng Zheng <[email protected]>
---
AGENTS.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/AGENTS.md b/AGENTS.md
index 5f56cacfb713..aebb2de64b39 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -203,6 +203,8 @@ It lists `master` and the latest major's release branches
the commit reached (e.
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]`).
+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]`.
+
Infer the PR title from the changes. If no ticket ID is given and the PR is
not draft, WIP, MINOR, or TRIVIAL, create one using `dev/create_spark_jira.py`,
using the PR title (without the JIRA ID and component tag) as the ticket title.
python3 dev/create_spark_jira.py "<title>" -c <component> { -t <type> | -p
<parent-jira-id> }
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
