voonhous opened a new pull request, #20376: URL: https://github.com/apache/hudi/pull/20376
### Describe the issue this Pull Request addresses `hudi_trino_ci.yml` runs on every PR. On PRs that do not touch the connector it still starts two runners: `detect-trino-changes`, and a `test-hudi-trino-plugin` job whose steps all skip. The no-filter design was there so a required check would never sit pending, but `test-hudi-trino-plugin` is no longer a required context. ### Summary and Changelog - The `pull_request` trigger now uses the same `paths` list as `push`. - Removed the `detect-trino-changes` job and the per-step `needs.changes.outputs.trino` guards. ### Impact PRs that do not touch the connector or its upstream modules start no Trino CI runner, two fewer than before. PRs that do touch them run the same build as before. ### Risk Level low. GitHub evaluates `paths` against at most 300 changed files, so a very large PR could skip this workflow; the old job checked every file. `test-hudi-trino-plugin` must stay out of the `.asf.yaml` required contexts. ### Documentation Update none ### 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 - [ ] 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]
