DanielLeens commented on PR #12937: URL: https://github.com/apache/seatunnel/pull/12937#issuecomment-6397063273
A small correction to the merge-gate wording in my previous review: the exact-head fork [Build](https://github.com/zhengxiang378928908-code/seatunnel/actions/runs/40073958586) remains SUCCESS for `fb104a5e123486fec8acb4d5bbb3f3608a5022fd`, but the Apache [PR signal workflow](https://github.com/apache/seatunnel/actions/runs/40073963444) is awaiting approval and no required Build result is attached to the PR's head rollup. So the remaining process is not just reviewer approval: a write-capable maintainer must also approve/inspect that workflow and attach/accept the corresponding exact-head result. My previous source-level clearance is unchanged; this is not another full source review or a request for a new source push. There is no failed test here to repair by an unrelated dependency change or a speculative sync. Branch drift is recorded separately, and a maintainer's final approval remains distinct from my read-only technical conclusion. -- 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]
