DanielLeens commented on PR #12902: URL: https://github.com/apache/seatunnel/pull/12902#issuecomment-6538166312
GitHub now reports an actual content conflict (CONFLICTING / DIRTY), superseding the earlier no-conflict snapshot on this unchanged head. Please reconcile the latest base while preserving both this PR's change and the intervening upstream work, then obtain required checks on the resulting commit. This request is based on the conflict, not the number of commits behind. Existing-head CI cannot validate that future resolution. My prior source conclusion remains clear for the reviewed scope; optional recommendations remain optional. The new conflict and current CI/repository approval gates are separate from that technical conclusion. My earlier statement that branch age alone required a normal base merge was too broad; the actual conflict is the demonstrated reason now. No upstream source cure for the earlier cancelled execution is inferred. Checked 2026-10-31T03:04:00.284020+00:00; unchanged head `91d1078a3790cf0bcdfbda5cd235c28ec8a95219`. [Notify test workflow](https://github.com/apache/seatunnel/actions/runs/39772126303/job/119801998688)=`SUCCESS`; [labeler](https://github.com/apache/seatunnel/actions/runs/39772126308/job/119801998121)=`SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/121186885183)=`IN_PROGRESS`. This is a discussion/CI clarification, not another full source review or an effective maintainer approval. Daniel has READ repository permission; a write-capable maintainer owns required approval/dismissal. -- 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]
