andygrove opened a new pull request, #6391: URL: https://github.com/apache/datafusion-comet/pull/6391
## Which issue does this PR close? Closes #6386. ## Rationale for this change The merge queue builds at most two entries at once. With a median full pipeline of 92 minutes (2026-09-11 to 2026-09-29), that caps a queue that never runs dry at roughly 30 merges a day. Approvals have been arriving at about 20 a day and merges landing at about 13.6, so the approved backlog keeps growing, and a batch of queued PRs takes 10 to 12 hours to drain. The data, and a simulation of other settings, are in the issue. ## What changes are included in this PR? - `.asf.yaml`: `max_entries_to_build` goes from 2 to 4, and its comment carries the current numbers. - The comment on the `merge_group` diff in `ci.yml` said `base_sha` covers every entry batched into the group. It is the queue commit of the entry ahead, so each entry's build covers only its own changes. The `ALLGREEN` comment in `.asf.yaml` now says why that makes `HEADGREEN` unsafe. - `ci.md` described the queue as building up to five pull requests as one batch. It now describes the per-entry builds. `.github/workflows/README.md` gets the new numbers. ## How are these changes tested? `python3 dev/ci/check-ci-config.py`, `actionlint` and prettier pass locally. The ruleset change takes effect when ASF's `.asf.yaml` processing applies it after the merge; the queue's GraphQL `configuration.maximumEntriesToBuild` should then read 4. -- 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]
