sdf-jkl opened a new pull request, #11788: URL: https://github.com/apache/arrow-rs/pull/11788
# Which issue does this PR close? No linked Arrow issue. Adapts the approach in [apache/datafusion#25591](https://github.com/apache/datafusion/pull/25591). # Rationale for this change Fork pull requests currently run their test suites upstream, consuming ASF's shared CI capacity before the merge queue validates the merged result. This change moves that initial test feedback to contributors' forks while retaining full upstream validation in the merge queue. # What changes are included in this PR? - Run all regular CI suites, excluding Miri, on fork branch pushes and manual runs. This includes documentation-only pushes. Superseded pushes to the same fork branch cancel earlier runs. - Keep lightweight checks upstream for fork PRs to `main`. Same-repository and release-branch PRs retain existing upstream testing; the merge queue still runs every suite, including Miri. - Show an informational `CI (fork)` check linking to the fork run for the current commit. A status bridge uses `workflow_run` and scheduled polling to discover results and reruns. It reads fork run metadata and writes upstream checks without checking out PR code or consuming PR artifacts. - Keep docs deployment upstream-only and add contributor setup instructions and CI configuration checks. Fork results are informational because contributors control their workflows. They do not replace the required merge-queue checks. # Are these changes tested? Routing and configuration tests cover fork pushes, PR targets, manual runs, and merge-queue validation. Bridge tests use mocked GitHub APIs to cover missing runs, reruns, stale commits, API failures, polling, and cancellation. All 8 routing/configuration tests and 29 bridge tests passed locally, along with workflow linting, spelling, and Markdown formatting checks. Hosted end-to-end validation remains outstanding. The bridge must be installed on a test repository's default branch to exercise `workflow_run` and scheduled updates. # Are there any significant user-facing changes? Contributors must enable Actions in their forks and update their branches to include these workflows. Results and reruns are available in the fork's Actions tab; the upstream status check may update later. No library API changes. -- 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]
