DanielLeens commented on PR #12678: URL: https://github.com/apache/seatunnel/pull/12678#issuecomment-6304985497
Thanks for trying that, @kalayciburak, and for not adding an empty commit just to retrigger it. You do not need one. The source side of this PR is unchanged from my last review, so the only open item is getting one `Build` run for head `03a99ef05ea6`. Here is what the apache-side check says. The `Build` check for this head is [`action_required`](https://github.com/apache/seatunnel/runs/118488200335) with the title "Workflow run detection failed". It is a pointer, because the real build runs in your fork, and it found no `Build` run there for this commit. A 422 when starting a workflow is consistent with GitHub Actions being disabled on the fork. The fork's disabled state is only visible to you, so I cannot confirm it from here, and I cannot start a run in your fork for you. Steps that should get it moving: 1. Open the **Actions** tab of `kalayciburak/seatunnel`. If you see the banner "Workflows aren't being run on this forked repository", click **I understand my workflows, go ahead and enable them**. If the tab shows no such button, check **Settings -> Actions -> General** and make sure Actions permissions are not set to "Disable actions". 2. If the tab or the account shows a billing or spending-limit hold, clear that first (**Settings -> Billing and plans**). GitHub keeps Actions off until it is cleared. 3. Select the **Build** workflow in the left sidebar, click **Run workflow**, and choose the branch `fix/prune-checkpoints-to-max-retained`. The `Build` workflow has a `workflow_dispatch` trigger for exactly this case, so no new commit is needed. 4. The scheduled `Update build status` workflow in Apache SeaTunnel then adopts that run for the PR check within about 15 minutes. Your earlier head `dcd60585` was green in your fork, so I expect this one to be a formality. If any job fails once it runs, please paste the job and test name here and I will help classify it. Once `Build` is green on this exact head, I have nothing else to ask. The final approval still needs a committer with write access. Thanks again for the patience! -- 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]
