goutamadwant opened a new issue, #12724: URL: https://github.com/apache/seatunnel/issues/12724
### Search before asking - [x] I had searched in the issues and found no similar issues. ### Description ASF Infra disables the `pull_request_target` trigger for ASF repositories from November 2026 (https://infra.apache.org/github-actions-policy.html). Two of our workflows use it: - `.github/workflows/add-label.yml` applies path labels to PRs. - `.github/workflows/notify_test_workflow.yml` creates the `Build` check that mirrors the fork CI run. **Why:** once the trigger is disabled, new and updated PRs get no labels and no `Build` check. **Before** ``` add-label.yml: on: pull_request_target notify_test_workflow.yml: on: pull_request_target ``` **After** (the pattern Infra recommends) ``` pr-signal.yml: on: pull_request, permissions: {}, one echo step add-label.yml: on: workflow_run of "PR signal", PR resolved from the payload notify_test_workflow.yml: on: workflow_run of "PR signal", same Build check ``` **Impact** - Labels and the Build check appear after the signal job completes, under a minute later than today. - First-time contributors keep getting labels and the Build check; their signal run is accepted while it waits for workflow approval. - `pr-signal.yml` must also be backported to maintained release branches, since `pull_request` workflows run from the PR merge ref. - No PR code is checked out or executed by the privileged jobs. ### Usage Scenario Every pull request. ### Related issues None. ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's Code of Conduct -- 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]
