You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by ru...@apache.org on 2026/05/11 11:30:44 UTC
(spark) branch branch-4.2 updated: [MINOR][INFRA][4.2] Fix `branch` input default in build_and_test.yml
This is an automated email from the ASF dual-hosted git repository.
zhengruifeng pushed a commit to branch branch-4.2
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/branch-4.2 by this push:
new a3209b0b7262 [MINOR][INFRA][4.2] Fix `branch` input default in build_and_test.yml
a3209b0b7262 is described below
commit a3209b0b7262664a9f9e496d8a7ef98b43b58f87
Author: Ruifeng Zheng <ru...@apache.org>
AuthorDate: Mon May 11 19:30:27 2026 +0800
[MINOR][INFRA][4.2] Fix `branch` input default in build_and_test.yml
### What changes were proposed in this pull request?
Update the default value of the `branch` workflow input in `.github/workflows/build_and_test.yml` from `master` to `branch-4.2`, and drop the stale `# Change 'master' to 'branch-4.0' in branch-4.0 branch after cutting it.` comment.
### Why are the changes needed?
When `branch-4.2` was cut from master, the comment in `build_and_test.yml` flagged that the default should be updated, but it wasn't. As a result, the `Build` workflow on pushes to `branch-4.2` invokes the reusable `build_and_test.yml` without an explicit `branch` input, which falls back to the default `master`. The `precondition` job then runs `actions/checkout` with `ref: master` against `apache/spark`, so the CI tests `master` rather than `branch-4.2`.
For example, [this `branch-4.2` push CI run](https://github.com/apache/spark/actions/runs/25591666487/job/75130390722) tested `master` instead of `branch-4.2`.
The same fix was already applied on `branch-4.0` and `branch-4.1`.
### Does this PR introduce _any_ user-facing change?
No. CI-only.
### How was this patch tested?
GitHub Actions on this PR. The default takes effect on subsequent pushes to `branch-4.2`.
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code
Closes #55796 from zhengruifeng/fix-branch-default-4.2.
Authored-by: Ruifeng Zheng <ru...@apache.org>
Signed-off-by: Ruifeng Zheng <ru...@foxmail.com>
---
.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 ffcc49eaec1b..99223efbf0dd 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.2
hadoop:
description: Hadoop version to run with. HADOOP_PROFILE environment variable should accept it.
required: false
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org