[4.x][SPARK-56959][INFRA] Remove branch input for some workflows#56001
Open
gaogaotiantian wants to merge 1 commit into
Open
[4.x][SPARK-56959][INFRA] Remove branch input for some workflows#56001gaogaotiantian wants to merge 1 commit into
gaogaotiantian wants to merge 1 commit into
Conversation
gaogaotiantian
changed the title
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
1 participant
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?
Remove the
branchinput for workflows that will be used for the decoupled CI schedulerWhy are the changes needed?
In the future, we will have a scheduler to trigger CI on a specific branch. These workflows will be used for scheduled CIs. They should not point to master branch.
build_and_test.ymlalready sets the default branch tobranch-4.xso we can just leave it empty.Notice that these workflows are not used at all at this moment.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI should pass but this PR alone should have no impact at all.
Was this patch authored or co-authored using generative AI tooling?
No.