Yicong-Huang opened a new pull request, #4624: URL: https://github.com/apache/texera/pull/4624
### What changes were proposed in this PR? The Build matrix jobs (`frontend`, `scala`, `python`, `agent-service`) were duplicated between `github-action-build.yml` and `reusable-build.yml`, and the two had drifted — `reusable-build.yml` was missing the recent license-check additions (npm bundle check, pip-licenses manifest, bundled-jar diff against LICENSE-binary, agent-service license manifest). Net change: **+238 / −416** lines. - Rename `reusable-build.yml` → `build.yml` (workflow name `Build`). It is now the single source of truth for the matrix steps, with the license-check additions ported in. - Rename `github-action-build.yml` → `required-checks.yml` (workflow name `Required Checks`). Replace the four inline matrix jobs with a single `build:` caller that `uses: ./.github/workflows/build.yml`. The `backport:` caller is unchanged; the `Required Checks` aggregator job's `needs:` shrinks from `[precheck, frontend, scala, python, agent-service, backport]` to `[precheck, build, backport]`. - Update `direct-backport-push.yml`'s `workflow_id` reference to the new filename. `.asf.yaml` continues to require only `Required Checks`, so the display-name change (matrix children gain a `build /` prefix) does not affect branch protection. ### Any related issues, documentation, discussions? Closes #4623 ### How was this PR tested? YAML parses locally for all three modified workflow files. Step parity between the new `build.yml` and the previous inline `github-action-build.yml` matrix jobs verified by side-by-side diff. The job will be exercised on this PR itself; matrix children appear under `Required Checks / build / …` and the `backport:` matrix continues to appear under `Required Checks / backport (...) / …`. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.7) -- 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]
