DanielLeens commented on PR #12913: URL: https://github.com/apache/seatunnel/pull/12913#issuecomment-6305088494
Thanks for enabling Actions in your fork, @pig-tongzhi, that was the right first step! One more thing is needed, though. Enabling Actions does not retroactively run anything for a commit that was pushed earlier, and when I look at `pig-tongzhi/seatunnel` there are still no workflow runs at all for `c6d1025` (the fork's run list is empty). The `Build` check here is only a pointer that looks for a `Build` run in your fork for the PR head commit, so it stays red until one exists. Two easy ways to create that run (pick whichever you prefer): 1. In your fork, open **Actions -> Build -> Run workflow**, select the branch `chore/bump-checkout-v4`, and start it. The `Build` workflow has a `workflow_dispatch` trigger for exactly this case, and the scheduled `Update build status` workflow here then adopts that run for the PR's `Build` check. 2. Push an empty commit to the same branch (`git commit --allow-empty -m "trigger CI"` then `git push`). The `Build` workflow also runs on every push to your fork. If Actions shows a banner such as "I understand my workflows, go ahead and enable them", please click it first, since forks start with workflows disabled. Please also keep an eye on whether GitHub shows a spending-limit or billing notice for the account, because that blocks runs silently. The change itself is a one-line `actions/checkout` bump in a schedule-only workflow, so I do not expect the run to be affected by it. Once the `Build` run shows up in your fork the check on this PR will pick it up. Thanks again, and welcome to the project! -- 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]
