[SPARK-56988] Add dev/spark_jira_utils.py#684
Closed
dongjoon-hyun wants to merge 1 commit into
Closed
Conversation
peter-toth
approved these changes
May 21, 2026
Member
Author
|
Thank you, @peter-toth ! |
Member
Author
|
Since this is irrelevant to CI result, I'm going to merge this. |
Member
Author
|
Merged to main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to add
dev/spark_jira_utils.pyby extracting the JIRA-related helpers out ofdev/create_jira_and_branch.py, mirroring Apache Spark's dev/spark_jira_utils.py.dev/create_jira_and_branch.pyis updated to import from this module and passes"Kubernetes"as the component.Why are the changes needed?
To keep the script aligned with Apache Spark's
dev/spark_jira_utils.pystructure and to allow reuse of the JIRA helpers from future dev scripts in this repository.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual test.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.7