voonhous opened a new pull request, #20476:
URL: https://github.com/apache/hudi/pull/20476

   ### Describe the issue this Pull Request addresses
   
   Every fork PR runs the full Java CI on the shared ASF runner pool, where it 
queues behind other ASF projects. With the merge queue as the merge gate, the 
per-push PR run can move to the contributor's fork, as apache/arrow-rs does.
   
   Part of #20471. Stacked on #20473: review the top commit only.
   
   ### Summary and Changelog
   
   - `ci.yml` runs on every branch push. Fork PRs to master skip both suites 
upstream; the contributor's push runs them on the fork's own runners, and the 
merge queue runs them on ASF runners before merge. Release-branch PRs and 
same-repository PRs keep upstream testing.
   - `Required Checks` accepts skipped suites only on a fork PR to master, and 
links the fork run from its summary.
   - New `fork_ci_status.yml`, adapted from arrow-rs: posts the fork run's 
result on the PR as the informational `CI (fork)` check (every 15 minutes, plus 
after each upstream CI run).
   
   <details>
   <summary>Smaller changes</summary>
   
   - Fork pushes cancel the older run of the same branch; upstream pushes stay 
keyed by SHA.
   - 47 node tests of the bridge script and of every `ci.yml` routing case run 
in `validate-pr-and-source`.
   - `.github/workflows/README.md` gains "Pull requests from forks": enable 
Actions on the fork, rebase onto master, push.
   </details>
   
   ### Impact
   
   Contributors need Actions enabled on their fork; until then `CI (fork)` says 
so. Fork PRs stop using ASF runners until they enter the queue.
   
   ### Risk Level
   
   medium. The merge gate becomes the merge queue; without it, fork PRs would 
merge on advisory results only, so this lands after the queue is live.
   
   ### Documentation Update
   
   `.github/workflows/README.md` updated; the website contribute page follows 
in an asf-site PR.
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable
   


-- 
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]

Reply via email to