DanielLeens commented on PR #11224: URL: https://github.com/apache/seatunnel/pull/11224#issuecomment-4901899944
Thanks for the ping. +1 to the CI-enable note above. The current `Build` check is still in `ACTION_REQUIRED`, and the actionable check URL is: https://github.com/apache/seatunnel/runs/84216026714 At this point I would not try to fix this by changing the PR source code. The lowest-cost next step is to enable/approve the CI workflow for this PR/fork first, then rerun the `Build` check. After CI is actually allowed to run, if the same lane fails with a real build/test error, please paste the new failing check link here and I can help narrow it down against that fresh result. One more metadata note I rechecked: this branch is also currently diverged from `dev` (`ahead_by=1`, `behind_by=102`), so after CI is enabled, syncing with the latest `dev` before rerunning the build will give the cleanest signal. -- 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]
