voonhous opened a new pull request, #20375: URL: https://github.com/apache/hudi/pull/20375
### Describe the issue this Pull Request addresses Every PR event starts a separate runner for each of four PR metadata checks: `validate-pr`, `validate-pr-title`, `validate-commit-coauthor` and, when `scripts/pr_compliance.py` changes, `run-tests`. Each check takes 4 to 9 seconds, so runner startup costs more than the checks themselves. Depends on #20374, which drops the two retired contexts from `.asf.yaml`. Merge that first. ### Summary and Changelog - New `pr_validation.yml` with a single `validate-pr` job. The PR description, `pr_compliance.py` self-tests, PR title and commit co-author checks run as steps in that job. - Every check step runs with `if: !cancelled()`, so one failure does not hide the others. The failed step's name says which check failed. - Removed `pr_compliance.yml`, `pr_title_validation.yml`, `commit_coauthor_validation.yml` and `update_pr_compliance.yml`. <details><summary>Behavior differences</summary> - The `pr_compliance.py` self-tests take about 30 ms, so they now run on every PR instead of behind a `paths` filter. - The co-author check now also runs when a PR's title or description is edited (one API call). - `actions/setup-python` is dropped: the scripts are stdlib-only and use the runner's `python3`. - Emoji in log lines replaced with plain text. </details> ### Impact Each PR event starts one runner for metadata checks instead of three or four. There is no change to what is checked. ### Risk Level low. The checks are copied verbatim. This PR's own `validate-pr` run exercises the new job. ### 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 - [ ] 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]
