nchammas opened a new pull request, #59862: URL: https://github.com/apache/spark/pull/59862
### What changes were proposed in this pull request? Restore the labeler removed in [apache/spark#54216](https://github.com/apache/spark/pull/54216) (SPARK-55433). - Run the official [`actions/labeler`](https://github.com/actions/labeler) every 15 minutes on open PRs updated in the last 12 hours. Only write when labels change. - Sort and refresh the path rules, including new `DECLARATIVE PIPELINES` and `UDF` labels. TODO before merging: - [ ] Create those two labels in the repository. The workflow can apply existing labels but cannot create them. ### Why are the changes needed? Labels make it easier to find PRs by area. ASF is [disabling][asf] `pull_request_target` in November 2026, so we cannot restore the old workflow. [asf]: https://infra.apache.org/github-actions-policy.html This scheduled scan is much simpler than having a signal-based set of workflows or using some custom labeler action. The official GitHub labeler action runs from `master` without checking out PR code, including for PRs against maintenance branches. 1 workflow; no custom actions; no backports needed. The 12-hour overlap covers delayed runs. Longer gaps can be backfilled with the command documented in the workflow. ### Does this PR introduce _any_ user-facing change? No. For contributors on GitHub only: PRs get area labels again, on a delay rather than immediately. Configured labels are kept in sync with changed files; unrelated labels such as `ai-review-requested` are preserved. ### How was this patch tested? Checked with actionlint/ShellCheck and local mocked-API tests against `actions/labeler@v7`: 68 path cases, pagination, input validation, label removal, preservation of unrelated labels, and zero writes on repeat runs. No writes were sent to GitHub. The scheduled trigger needs verification after merge, since it only runs from `master`. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: GitHub Copilot -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
