HeartSaVioR opened a new pull request, #57740: URL: https://github.com/apache/spark/pull/57740
### What changes were proposed in this pull request? `branch-4.3` inherited its build workflows from `branch-4.x` when it was cut, so they still identify themselves as `branch-4.x`. Apply the convention that the other release branches (`branch-4.2`, `branch-4.1`) already follow: - drop the branch token from the nine `build_*.yml` workflow titles, e.g. `"Build / Maven (branch-4.x, Scala 2.13, Hadoop 3, JDK 17)"` becomes `"Build / Maven (Scala 2.13, Hadoop 3, JDK 17)"`. The branch is implied by where the file lives, and the old names collided confusingly with the real `branch-4.x` runs in the Actions UI and in check-run names; - point the `branch` input default of both reusable workflows at this branch: `build_and_test.yml` from `branch-4.x` and `maven_test.yml` from `master`, both to `branch-4.3`. The `maven_test.yml` default is the `branch-4.3` instance of SPARK-58537: the callers pass no `branch:` input, so the Maven workflows were building `master` rather than this branch. On `branch-4.2` and `branch-4.1` both reusable workflows default to their own branch, which is why their callers correctly need no explicit input. ### Why are the changes needed? branch-4.3 mistakenly refers to master branch in CI, which should have been fixed. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? scheduled CI will confirm with it. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Opus 5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
