Yicong-Huang opened a new pull request, #5036:
URL: https://github.com/apache/texera/pull/5036
### What changes were proposed in this PR?
This PR enables GitHub merge queue for the default branch through
`.asf.yaml` rulesets so ready PRs no longer need to repeatedly update against
`main` after other PRs land.
The ASF ruleset configuration adds the required `meta.environment:
github_rulesets` section, creates a default-branch merge queue ruleset with the
existing required checks and review requirement, and disables repository
auto-merge so PRs are queued manually. The previous `protected_branches.main`
configuration is replaced by the default-branch ruleset to avoid keeping the
old strict branch-up-to-date requirement alongside merge queue.
This also adds the `merge_group` event to the required workflows so GitHub
Actions report the required checks for merge queue runs. The PR title workflow
keeps validating pull request titles on `pull_request_target` and no-ops on
`merge_group`, since title validation must happen before a PR enters the queue.
### Any related issues, documentation, discussions?
Closes #4553
### How was this PR tested?
Ran local configuration checks:
```bash
ruby -e 'require "yaml"; [".asf.yaml",
".github/workflows/github-action-build.yml",
".github/workflows/check-header.yml", ".github/workflows/lint-pr.yml"].each {
|f| YAML.load_file(f); puts "ok #{f}" }'\nruby -e 'require "yaml";
cfg=YAML.load_file(".asf.yaml"); abort "missing meta" unless cfg["meta"] &&
cfg["meta"]["environment"] == "github_rulesets";
mq=cfg["github"]["rulesets"].find { |r| r["name"] == "Merge Queue" }; abort
"missing merge queue" unless mq; abort "main branch protection still present"
if cfg.dig("github", "protected_branches", "main"); puts "asf ruleset sanity
ok"'\ngit diff --check\n```\n\nNo automated runtime tests were added because
this PR only changes repository/GitHub Actions configuration.\n\n### Was this
PR authored or co-authored using generative AI tooling?\nGenerated-by: OpenAI
Codex (GPT-5)\n
--
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]
