DanielLeens commented on PR #10238: URL: https://github.com/apache/seatunnel/pull/10238#issuecomment-5412501001
Thanks @SEZ9 -- I independently re-checked the live PR state just now rather than taking the summary at face value: the head is still `2952d05534a0f828f26de20877d19ad4115f5771` (confirmed via the PR API), `mergeable=false` / `mergeable_state=dirty` so the conflicts with `dev` are indeed still unresolved, and the only check-run attached to this head is still the `Build` job from 2026-07-26 (https://github.com/apache/seatunnel/runs/89797556787, conclusion `failure`) -- no newer CI has run against this head. So the status reported here checks out against what I see directly from the API. Since nothing has changed since my last update and we've now confirmed the same status for several days running, repeating the full checklist daily isn't adding new information for @LiJie20190102. To keep it simple: the remaining work is entirely mechanical -- sync the branch with the latest `dev`, resolve the merge conflicts, push the refreshed head, and let `Build` run against the current diff. Once that refreshed head lands, I'll do the follow-up review pass myself; no need to re-ping this thread again until then. -- 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]
