lxcxjxhx commented on PR #13119: URL: https://github.com/apache/seatunnel/pull/13119#issuecomment-6621000659
Follow-up with the evidence, because the fork side is now clean but the check still does not appear on the PR. **Fork side — done.** Actions were indeed not registered (`actions/workflows` reported `total_count: 0` even though `actions/permissions` said `enabled: true`). Re-issuing the PUT registered all 20 workflows, and `Build` has now completed successfully on all four of my doc branches: | branch | run | result | |---|---|---| | `docs/zh-key-source-files` (#13119) | [41756137043](https://github.com/lxcxjxhx/seatunnel/actions/runs/41756137043) | success | | `docs/fix-multimodal-anchor` (#13123) | [41756226722](https://github.com/lxcxjxhx/seatunnel/actions/runs/41756226722) | success | | `docs/mem0-sink-options` (#13113) | [41756367300](https://github.com/lxcxjxhx/seatunnel/actions/runs/41756367300) | success | | `docs/fix-changelog-table` (#13117) | [41756376318](https://github.com/lxcxjxhx/seatunnel/actions/runs/41756376318) | success | **Base repo side — waiting on approval.** The `PR signal` run for this PR (41755795271, head `6bb003de`) is `action_required` with **zero jobs**: GitHub holds workflows for a first-time contributor until a maintainer approves them. That breaks the chain the repo relies on — `notify_test_workflow.yml` triggers on `workflow_run: PR signal completed` and is what creates the initial `Build` check run, and `update_build_status.yml` can only patch an existing one (it logs `Skip PR: no eligible Build check run` and returns). So the scheduled updater cannot bootstrap the check either. Two of my PRs are in that state right now (#13119 and #13123). If you click "Approve and run workflows" on them, the signal will complete, the `Build` check will be created, and the updater will adopt the green fork run on its next 15-minute tick. I have no way to approve my own pending run. Thanks again for walking me through the setup — the fork-side fix is recorded for the rest of my PRs here. -- 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]
