This is an automated email from the ASF dual-hosted git repository.

dongjoon pushed a commit to branch branch-4.1
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/branch-4.1 by this push:
     new 5f3fe121570b [SPARK-54135][INFRA][4.1] Add GitHub Action jobs for 
branch-4.1
5f3fe121570b is described below

commit 5f3fe121570bb8c74f5d64d7a4fea5305bb7221b
Author: Dongjoon Hyun <[email protected]>
AuthorDate: Sun Nov 2 08:29:10 2025 -0800

    [SPARK-54135][INFRA][4.1] Add GitHub Action jobs for branch-4.1
    
    ### What changes were proposed in this pull request?
    
    This PR aims to add `GitHub Action` jobs to branch-4.1.
    
    ### Why are the changes needed?
    
    To trigger CIs on branch-4.1 PR and commits.
    
    ### Does this PR introduce _any_ user-facing change?
    
    No.
    
    ### How was this patch tested?
    
    Manual review.
    
    ### Was this patch authored or co-authored using generative AI tooling?
    
    No.
    
    Closes #52834 from dongjoon-hyun/SPARK-54135.
    
    Authored-by: Dongjoon Hyun <[email protected]>
    Signed-off-by: Dongjoon Hyun <[email protected]>
---
 .github/workflows/build_and_test.yml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/.github/workflows/build_and_test.yml 
b/.github/workflows/build_and_test.yml
index 3776a116fd78..3ba71108f553 100644
--- a/.github/workflows/build_and_test.yml
+++ b/.github/workflows/build_and_test.yml
@@ -30,8 +30,7 @@ on:
         description: Branch to run the build against
         required: false
         type: string
-        # Change 'master' to 'branch-4.0' in branch-4.0 branch after cutting 
it.
-        default: master
+        default: branch-4.1
       hadoop:
         description: Hadoop version to run with. HADOOP_PROFILE environment 
variable should accept it.
         required: false


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to