Skip to content

[MINOR][INFRA] Clarify JIRA reuse for follow-up PRs - #57818

Open
zhengruifeng wants to merge 5 commits into
apache:masterfrom
zhengruifeng:minor/clarify-followup-pr-jira
Open

[MINOR][INFRA] Clarify JIRA reuse for follow-up PRs#57818
zhengruifeng wants to merge 5 commits into
apache:masterfrom
zhengruifeng:minor/clarify-followup-pr-jira

Conversation

@zhengruifeng

Copy link
Copy Markdown
Contributor

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

Comment thread AGENTS.md Outdated

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]`).

If a PR follows up on one or more earlier PRs, reuse their existing JIRA ticket(s). Do not create a new JIRA ticket for the follow-up PR.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there is one exception: if the original PR is already released, then we need a new JIRA as the released version is different

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in that case, I think we should not use a [FOLLOWUP] PR, IIRC @dongjoon-hyun

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants