DanielLeens commented on PR #12165: URL: https://github.com/apache/seatunnel/pull/12165#issuecomment-6514268681
Thanks @SEZ9. I agree with keeping the follow-up scope separate. The current reviewed head is source-clear and Build-green, but GitHub still reports actual merge conflicts. The contributor must sync the latest base and resolve those conflicts while preserving both sides, then obtain CI on the resulting new head for complete re-review. Final effective approval belongs to a write-capable maintainer. Checked 2026-10-30T03:30:37.151775+00:00; head `a932e27a757519fe74a26cb2920966cad853aead`. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40463709659/job/122617757074)=`SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/122968422970)=`SUCCESS`. Base `dev`, `diverged`, ahead 15/behind 64; merge `dirty`. This is an unchanged-head discussion/CI clarification, not another full source review or an effective approval. Daniel has READ repository permission. -- 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]
