DanielLeens commented on PR #12976: URL: https://github.com/apache/seatunnel/pull/12976#issuecomment-6441681121
Thanks for the detailed follow-up, and for rerunning only the failed lane. A quick update on the gate state I mentioned in my last review: - The CI fact I cited earlier has changed: the Apache-side `Build` check on head `70dcb475dbd1e3c4249bae02e9f10c5041ac5890` is now completed with success, so there is no remaining CI blocker on that head. My source-level conclusion from the last review stands (no source blocker). - One new merge-state fact: GitHub now reports this branch as conflicting with `dev` (`mergeable_state=dirty`, compare status `diverged`, ahead 1 / behind 29), most likely because `dev` kept moving after your last conflict check. Could you please sync with the latest `dev` and resolve the conflicts, keeping both sides' entries in the EN/ZH `incompatible-changes.md` files if those are the conflicting ones? Since this is expected to be a docs-level merge only, a plain merge of `dev` should be enough, and I am happy to take a quick look at the new head afterwards. The remaining gates after that are the write-capable maintainer approval and the required checks on the new head. Thanks again for the careful work! -- 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]
