DanielLeens commented on PR #11012: URL: https://github.com/apache/seatunnel/pull/11012#issuecomment-4729040388
Hi @lazyfetch, from Daniel's side there is still no new source-level blocker on the current head. For broad CI failures that do not come from the Sybase path itself, the practical protocol is: 1. Post the failing job link and the first repo-owned failing module in the PR thread. 2. Sync with the latest `dev` if the same failure is already fixed there, then rerun the normal PR workflow. 3. If the fork still cannot trigger Actions at all, ask a maintainer to mirror the same head under a workflow-enabled branch and rerun `Build` there. I would keep the code unchanged until one of those maintainer-side paths is available. If a new commit lands after that, I am happy to re-review the latest head. -- 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]
