DanielLeens commented on PR #12907: URL: https://github.com/apache/seatunnel/pull/12907#issuecomment-6473603797
Thanks for confirming the Build and for preparing a resolution that preserves both migration entries. A real conflict must be resolved before the final approval/queue step: preserving an old approval should not leave an unmergeable head waiting indefinitely. Please sync the latest dev and resolve those documentation conflicts first, keeping both entries, then run checks on the resulting head. A committer can review that mergeable head. My earlier use of 'approved' described technical clearance; it was not an effective write-level approval. Gate snapshot (2026-10-28T15:46:19+00:00), head `baa9accfdbf686010e752a9241aadd0f94735f32`: [Build](https://github.com/apache/seatunnel/runs/122617993326) is `SUCCESS`. CI was previously the only remaining technical gate in my conclusion; CI is now passing, so that CI objection is withdrawn and my technical conclusion is clear to proceed. Daniel currently has READ permission. I have not changed the effective GitHub review state to APPROVED; a write-capable maintainer must perform the final approve/dismiss action required by branch protection. Separately, GitHub reports merge conflicts with `dev`. Please sync the latest base and resolve the conflicts first; the resulting new head needs checks and re-review. This conflict gate is independent of CI and existing source findings. -- 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]
