Yicong-Huang opened a new pull request, #7042: URL: https://github.com/apache/texera/pull/7042
### What changes were proposed in this PR? Retune the `merge_queue` ruleset in `.asf.yaml` to speed up the merge queue: | Parameter | Before | After | Why | | --- | --- | --- | --- | | `grouping_strategy` | ALLGREEN | HEADGREEN | Merge a whole batch on one green head-group run instead of one green run per queued PR; also cuts flaky-test exposure from N draws per batch to 1. | | `max_entries_to_build` | 5 | 2 | Under HEADGREEN, non-head speculative builds no longer gate merging; keep one in flight for pipelining, save shared ASF runner quota (each group runs the full ~20-job matrix). | | `min_entries_to_merge` | 2 | 2 (was 1) | Batch PRs so one full CI run merges several at peak times. | | `min_entries_to_merge_wait_minutes` | 5 | 3 | Short batching window; off-peak a lone PR waits at most 3 minutes. | | `check_response_timeout_minutes` | 30 | 45 | Headroom for runner-queue delays so a late-reporting check is not misjudged as failed. | `merge_group` events run every CI stack regardless of PR labels (`precheck.yml` only filters on `pull_request` events), so each avoided group build saves a full-matrix run. Backport discovery is unaffected: `direct-backport-push.yml` already iterates every commit in a multi-PR push. ### Any related issues, documentation, discussions? Closes #7041. Parameters follow the GitHub rulesets `merge_queue` schema: https://docs.github.com/en/rest/repos/rules ### How was this PR tested? - Config-only change; validated `.asf.yaml` parses with `python3 -c "import yaml; yaml.safe_load(open('.asf.yaml'))"`. - Cross-checked parameter names and enum values against the GitHub rulesets `merge_queue` schema. - Effect on the live ruleset is applied by ASF infra after merge; will observe the next few queue batches. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Fable 5) -- 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]
