DanielLeens commented on PR #12705: URL: https://github.com/apache/seatunnel/pull/12705#issuecomment-6158069494
Thanks for flagging this, and for pushing the retrigger commit. I checked the head (`3a68380`): the new commit is empty (its tree is identical to `584d5e8`, which I already reviewed in full), so my previous review still applies as-is and the only remaining gate is CI. What I see: the apache-side `Build` check is `action_required` with "Workflow run detection failed", and your fork has no `Build` run for this head. Notably the fork did run `Build` for other branches around Oct 6-9, so GitHub is simply not creating runs for the recent pushes. The lowest-cost things to try, in this order: 1. Open the **Actions** tab of your fork (`Asthenia0412/seatunnel`). If there is an enable banner, or a notice about a billing / spending-limit hold on the account, resolve that first; while Actions is blocked no push will start a run, which would explain why empty commits do nothing. 2. Sync the branch with the latest `dev` (it is well behind now, which I had also noted in my earlier review) and push. Since #12720, `build_main.yml` on `dev` has a `workflow_dispatch` trigger, so after the sync you can also go to Actions -> **Build** -> **Run workflow**, pick this branch, and the scheduled `Update build status` workflow will attach that run to the PR check within about 15 minutes. Your branch does not have that trigger yet, so the manual button will not appear until you sync. 3. If a run still does not appear after steps 1 and 2, please paste a link to your fork's Actions page here and I will help narrow it down. No source changes are needed for this; the code-side review items from my last round are unchanged. Happy to re-check once a `Build` run exists! -- 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]
