chore(ci): rename CI names for test-ci rules
#3940
Merged
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
There was a problem hiding this comment.
Pull Request Overview
This PR renames CI job names in the ASF configuration file to standardize naming conventions for test-ci branch rules. The changes update job names from domain-specific terms to more generic ones.
- Renames "gui" jobs to "frontend" for better clarity
- Renames "core" job to "scala" for consistency
- Renames "python_udf" jobs to "python" for simplification
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
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 PR?
This PR changes the desired CI rule names against
test-cibranch to test. This change has to be pushed tomainto take effect. Will updatetest-ci's GitHub Action workflow separately (using #3936).Any related issues, documentation, discussions?
related to #3939.
How was this PR tested?
Manual tests.
Was this PR authored or co-authored using generative AI tooling?
No.