DanielLeens commented on PR #13119: URL: https://github.com/apache/seatunnel/pull/13119#issuecomment-6624361910
Thanks @lxcxjxhx, and thanks for digging into this so carefully. Your analysis matches what I see: - Your fork `Build` run on this exact head `6bb003de` completed successfully: https://github.com/lxcxjxhx/seatunnel/actions/runs/41756137043 - The apache-side `PR signal` run for this head (https://github.com/apache/seatunnel/actions/runs/41755795271) is `action_required` with 0 jobs, so it never reached `notify_test_workflow.yml`, which is what creates the `Build` check run that `update_build_status.yml` later updates. For comparison, the `PR signal` run of #13085 sat in the same state until a maintainer approved it, then the `Build` check attached normally. So there is nothing more to do on your side, and no new commit is needed. I only have read access here, so I cannot click "Approve and run workflows" myself; a committer with write access needs to approve the pending workflow run on this PR (and on #13123). After that the `Build` check should attach and pick up your green fork run. My approval of the doc change stands for this head. Thanks again for the patience and the clear write-up! -- 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]
