[SPARK-52004] Improve publish_snapshot_chart GitHub Action job to support branches
#185
Conversation
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
viirya
approved these changes
May 5, 2025
Member
Author
|
Thank you, @viirya . BTW, when you have some time, could you participate votes, please? Thank you in advance~ |
Member
Author
|
Merged to main. |
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 improve
publish_snapshot_chartGitHub Action job to support branches.Why are the changes needed?
Previously, the job supports only
mainbranch. After this PR,branch-0.1is added to the matrix.However, this PR should land at only
mainbranch because GitHub Action supports the schedule job only atmainbranch.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual review. This should be tested after merging.
Was this patch authored or co-authored using generative AI tooling?
No.