DanielLeens commented on PR #12578: URL: https://github.com/apache/seatunnel/pull/12578#issuecomment-6341315921
Thanks @hutiefang76, that is exactly the run I had in mind, and thank you for not adding a source change or an empty commit. Current state, as I can read it right now: the [fork run](https://github.com/hutiefang76/seatunnel/actions/runs/39775915510) reports head `ef53a70c6f72f5f6ae7c31fcc57b541eb3c849f3`, event `workflow_dispatch`, and is still `queued` (the `changes`, `Code style`, `Dead links` and `License header` jobs have not started, so there is no test result yet). The only completed checks on the PR itself are `labeler` (success) and `Notify test workflow` (failure, the earlier GitHub API 500). One expectation to set: a `workflow_dispatch` run in the fork is good evidence of how this exact commit behaves, but GitHub does not attach it to the PR as the required `Build` check, which is tied to a `pull_request` run. So even if it finishes green, a maintainer will still need to retry the failed notification or otherwise re-trigger the PR-bound check before the merge gate can clear. Please keep the link here and post the final result when it finishes. My source-level conclusion is unchanged: no source blockers. -- 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]
