[raulcd]

Rationale for this change

GitHub is going to block the pull_request_target event from the 2nd of December:

• https://github.blog/changelog/2026-11-02-pull_request_target-blocked-by-default-december-2/

What changes are included in this PR?

Remove the dev_pr.yml workflow and change it with configration for boring-cyborg app.

Are these changes tested?

No

Are there any user-facing changes?

Not for users.

For devs, issues are not auto-assigned anymore.
Automatic draft conversion when bad PR title and automated message with explanation of wrong PR titles won't appear anymore.

Was AI used for this PR?

In accordance to the AI generation guidelines, please disclose below whether and how AI was used in this PR.

PR code and description written by:

• Human
• AI

Reviewed before submission by:

• Human
• AI
• Not reviewed

• GitHub Issue: [CI] Remove pull_request_target event workflows #55392

[github-actions]

⚠️ GitHub issue #55392 has been automatically assigned in GitHub to PR creator.

[raulcd]

@kou @pitrou I've been exploring removing the dev_pr.yml workflow with the cyborg-app.
The biggest thing we lose is the auto-assign of issues. We could have a check to validate the issue is assigned but as users can't assign the issue themselves (unless they have triage) and we removed the ability to use take this would just give us more maintenance to maintainers.
We could at merge time (on the merge script) assign the issue to the PR author and if it fails (user never commented on issue) we can just ignore the assignation as the important bit is the Author of the PR and this is what we count as contribution credit.
What are your thoughts?

I can also split this PR into multiple PRs and only move the labeler first and then the title check, issue link so it's easier to review.

[pitrou]

Can we see what boring-cyborg looks like on an actual PR?

[raulcd]

Can we see what boring-cyborg looks like on an actual PR?

This PR on arrow-rs shows how the label was added by the cyborg-app:

• test(arrow-cast): move interval and duration cast tests to integration suite arrow-rs#12151

As per testing all the functionality on our repo, unfortunately we can't until this is merged on main.

I can change this to only replace the labeler and we can validate the rest of the functionality one feature at a time or I could try installing the app on my fork to show it.

[Reranko05]

@raulcd With Boring-Cyborg, which workflows will run for first-time contributors before a maintainer approves their workflow runs?

(I think the AI disclosure check(#55361) should run before approval so that we can close PRs that fail the disclosure policy without requiring maintainers to approve their workflows first.)

[raulcd]

@raulcd With Boring-Cyborg, which workflows will run for first-time contributors before a maintainer approves their workflow runs?

To be honest, I don't know how can I check that.

[pitrou]

Ok, a question: if someone manually adds or removes a label, does boring-cyborg attempt to undo the change?

[pitrou]

Also, at some point it would be nice if there was a system to automatically correct the PR title to include the selected components.

[kou]

+1

Let's try boring-cyborg. If we have missing features, we can improve boring-cyborg because boring-cyborg is an OSS.