ump45nose opened a new pull request, #2891:
URL: https://github.com/apache/datafusion-sqlparser-rs/pull/2891

   Dialects: none
   
   ## What
   
   Migrates the dialect labeler off `pull_request_target`, which ASF infra is 
disabling and GitHub will block by default on 2 December 2026.
   
   - Add a permissionless `pull_request` signal workflow (`opened` / `edited` / 
`reopened` / `synchronize`).
   - Run the existing dialect labeler from the default branch on that 
workflow's `workflow_run` `requested` event.
   - Look up the current open pull request(s) for the signal's head repository 
and branch instead of trusting pull request code or an artifact.
   - Leave the `issues` and `issue_comment` paths unchanged.
   
   `edited` is included so a title or `Dialects:` line update still applies 
labels, matching the current behavior. The `requested` event fires even while a 
first-time contributor's checks wait for approval.
   
   This follows the current approach in apache/datafusion#26683 rather than 
uploading a pull request number artifact: that pull request moved to a signal 
plus an API lookup, which avoids treating PR-produced data as input.
   
   The new pull request path takes effect after this change is on the default 
branch. Until then, the existing `pull_request_target` workflow on `main` 
continues to label pull requests.
   
   Fixes #2818
   
   ## Tests
   
   - `node --check` on both labeler scripts
   - Mocked Node checks for: labeling from an explicit pull object, the 
unanswered-PR prompt, the unchanged `issue_comment` path, and 
`pull_requests_of_run.js`
   - No Rust changes, so `cargo test` / `fmt` / `clippy` were not rerun
   
   ## AI assistance
   
   Prepared with AI assistance. I reviewed the workflow change, the script 
updates, and the referenced DataFusion pattern before opening this PR.
   


-- 
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]

Reply via email to