voonhous opened a new pull request, #20663: URL: https://github.com/apache/hudi/pull/20663
### Describe the issue this Pull Request addresses On #20660 the fork has Actions turned off, so no fork run exists, yet the PR shows a grey `CI (fork)` check next to a green `Java CI result` and offers "Merge when ready". `CI (fork)` reports a missing run as `neutral` unless `bot.yml` itself is disabled, and a fork with Actions turned off in its settings still lists its workflows as active. Follow-up to #20471. ### Summary and Changelog - A missing fork run now reports `action_required` (shown as failing), except when the PR changes only docs and images, which the push filter of `bot.yml` skips. Failed fork runs already report `failure`. - `bot.yml` gets `workflow_dispatch`, so a contributor can start a fork run with Run workflow. After enabling Actions, an empty commit starts no run because of the path filter. - The check text and the workflows README say so, and that committers queue a fork PR only once `CI (fork)` is green. <details> <summary>Details</summary> - The docs-only test reads the PR's files (renames count both paths); a PR at the files API limit of 3000 counts as more than docs. - `fork_ci_status.yml` and `fork_coverage_bridge.yml` already accept `workflow_dispatch` runs. - Node tests: 74 in test-fork-ci-status.cjs (7 docs-only cases, and the docs paths pinned to the push filter of `bot.yml`). </details> ### Impact Fork PRs without a fork run show a failing `CI (fork)` check. It stays non-required. ### Risk Level low. Only the check's conclusion and text change, plus a manual trigger. ### Documentation Update `.github/workflows/README.md` updated. ### Contributor's checklist - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Enough context is provided in the sections above - [x] Adequate tests were added if applicable -- 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]
