DanielLeens commented on PR #12269: URL: https://github.com/apache/seatunnel/pull/12269#issuecomment-6975956731
Thanks for supplying the actual dispatch error. That corrects the next step in my previous review: a workflow listed as active does not prove that GitHub will permit repository Actions execution. The HTTP 422 you reported needs the fork owner or GitHub account support to lift the repository restriction first; repeatedly dispatching the same workflow, adding an empty commit, or changing connector code will not resolve it. Once execution is restored, run the existing Build on this same branch and link the result for `8cef2c6783550503fa9a3b0caebb6bc74d9bfb21`. The current API still returns no exact-head Build, and my source assessment remains clear. A write-capable maintainer review is a separate gate. -- 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]
