dongjoon-hyun opened a new pull request, #399:
URL: https://github.com/apache/spark-connect-swift/pull/399
### What changes were proposed in this pull request?
Make `build_and_test.yml` a reusable (`workflow_call`) workflow and add
Apache
Spark's fork-based CI status mechanism:
- `build_main.yml` — runs on `push` to all branches and calls
`build_and_test.yml`.
- `notify_test_workflow.yml` — on `pull_request_target`, creates a `Build`
check
on the PR that points to the fork's run.
- `update_build_status.yml` — every 15 minutes, syncs the `Build` check from
the
fork's run.
- Add `images/workflow-enable-button.png` used by the notify message, and
repoint
the README badge and `AGENTS.md` to `build_main.yml`.
### Why are the changes needed?
Run the heavy test matrix in contributors' forks and mirror only a single
`Build`
status check upstream, instead of running the matrix in the upstream repo on
every
PR. This matches the Apache Spark main repository.
### Does this PR introduce _any_ user-facing change?
No. CI and documentation only.
### How was this patch tested?
Static verification of the cross-workflow wiring: the `Run / License Check`
check-run name, the shared `Build` check name, and the `run_id` passed from
`notify` to `update`. Full behavior takes effect only after merge to `main`,
since
the `pull_request_target`/`schedule` workflows and `main`-pinned URLs
resolve from
the default branch.
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 4.8)
--
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]
