DanielLeens commented on PR #11500: URL: https://github.com/apache/seatunnel/pull/11500#issuecomment-6514224243
Thanks @SEZ9. I confirm the same exact-head green checks and agree that the earlier CI concern is cleared. My technical source conclusion is also clear; a write-capable maintainer must still issue the effective approval/merge decision. This reply is not a new full review or an APPROVED event, and no extra commit or retry is requested. Snapshot 2026-10-30T03:23:54.162485+00:00: head `85dccfade17340aa8c1ca08bc4c80775a4bc0621`; [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40701329545/job/122861638223) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/122916127285) = `SUCCESS`. Base `dev`; comparison `diverged`, ahead 27, behind 18; merge state `blocked`. Behind/diverged alone is recorded metadata and does not add a sync request. This is an unchanged-head discussion/CI clarification, not a new complete source review, an effective approval or a dismissal of historical requested changes. -- 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]
