DanielLeens commented on issue #11543: URL: https://github.com/apache/seatunnel/issues/11543#issuecomment-5065084108
Thanks for splitting merge queue into its own focused issue. I checked the current repository state on July 24, 2026. PR #11532 was merged on July 23, 2026, so the strict required `Build` check is now in place, but I do not see a dedicated `merge_group` workflow or any queue-specific handling in the repository yet. That means this is still a real follow-up design and implementation item rather than something already covered in `dev`. The direction is useful, but it should stay as a focused CI/design track under #11513 instead of jumping straight to enforcement on `dev`. Before implementation starts, the most important points to make explicit are: 1. which exact check name will be required for `merge_group`, and how it differs from the ordinary PR-head `Build` 2. whether ASF/GitHub settings already allow Merge Queue for this repository, and what the rollback path is if queue CI becomes unstable 3. how base-branch flakes will be separated from PR-introduced failures, so the queue does not become a noisy serial bottleneck 4. whether the first rollout is strictly `single-entry queue + shadow branch`, with documented dequeue, retry, bypass, and timeout rules If those boundaries are written down and the `[email protected]` discussion confirms the policy side, this looks like a reasonable child issue to keep advancing under #11513. -- 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]
