sdf-jkl commented on PR #55318: URL: https://github.com/apache/arrow/pull/55318#issuecomment-6502556527
@rok @raulcd @kou — would you support exploring a merge queue for `main`? I've put together this draft prototype to make the proposal concrete. Early feedback on the direction would help; it is not ready for review or merge. The proposed upstream gate runs the regular language and tooling suites on the combined candidate before merging. This could provide the final upstream validation for the fork-CI experiment in #55314. This draft alone adds CI work; reducing PR build duplication would be a later step. The [fork demonstration](https://github.com/sdf-jkl/arrow/actions/runs/40912033050) confirms that the gate accepts successful suites and rejects failed or skipped suites. The [full fork run](https://github.com/sdf-jkl/arrow/actions/runs/40912073031) has an ORC download failure and queued macOS jobs, so it isn't green. Native queue behavior still needs an organization-owned sandbox. Would the regular suite be a reasonable initial required set, and would using GitHub's queue UI be acceptable while `merge_arrow_pr.py` remains unable to enqueue? The draft starts with one candidate at a time. Nothing has been enabled upstream. -- 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]
