voonhous opened a new pull request, #20474: URL: https://github.com/apache/hudi/pull/20474
### Describe the issue this Pull Request addresses Two PRs that each pass CI can still break master together, since nothing re-tests them against the master they land on. This turns on GitHub's merge queue for master so every PR is tested against the latest master plus the PRs queued ahead of it before it lands. Part of #20471, closes #19612. Merge only after #20473 has merged and shown `Required Checks` reporting on PRs. ### Summary and Changelog - `.asf.yaml` gains a merge-queue ruleset for master: squash, two groups building at a time, up to five green entries merged together, 300 minute check timeout, apache/root (ASF Infra) as bypass actor. The payload is identical to the one apache/arrow-rs runs; apache/iceberg-rust, apache/iceberg-python and apache/datafusion-comet use the same mechanism, so no ASF infrastructure is involved. - `Required Checks` (from `ci.yml`, #20473) becomes required next to `validate-pr-and-source`. ### Impact - Committers merge with "Merge when ready"; the PR lands once its queue run passes, about one full Java CI run later. - Every open PR needs one new push (or a close and reopen) before it reports `Required Checks`. - A queue group invalidated mid-run still runs to the end (workflows cannot react to the `destroyed` event), so a failed entry can cost one extra Java CI run. ### Risk Level medium. A wrong context name or a rejected ruleset would block merges; apache/root can bypass the queue, and reverting this file restores today's settings. ### Documentation Update none ### 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 - [ ] 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]
