You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Dev] Make PRs that doesn't match our PR format draft automatically #50379
Sounds reasonable to me. I think the obvious offenders are the agent generated ones without human intervention, maybe the efforts from @thisisnic on adding new AGENTS.md files help with those.
Comments welcomed on #50375 if there are any other common AI failures we can try to account for.
Do we also perhaps want to add an auto-comment for issues which have been created without our issue template, and lack a "Type" and "Component" label as there are AI-generated ones which look like this and so are less likely to get in front of the relevant person.
Activity
raulcd commentedon Jul 6, 2026
Sounds reasonable to me. I think the obvious offenders are the agent generated ones without human intervention, maybe the efforts from @thisisnic on adding new AGENTS.md files help with those.
rok commentedon Jul 6, 2026
Agreed! We just want to give clear human readable feedback to not introduce an unnecessary friction point.
thisisnic commentedon Jul 6, 2026
Comments welcomed on #50375 if there are any other common AI failures we can try to account for.
Do we also perhaps want to add an auto-comment for issues which have been created without our issue template, and lack a "Type" and "Component" label as there are AI-generated ones which look like this and so are less likely to get in front of the relevant person.
kou commentedon Jul 10, 2026
@Reranko05 Do you want to work on this?
Reranko05 commentedon Jul 10, 2026
@kou Sure! I'll take a look.
Merge pull request #4 from Reranko05/apachegh-50379-pr-format
apacheGH-50379: Convert invalid PRs to draft automatically
apacheGH-50379: Convert invalid PRs to draft automatically
GH-50379: [Dev] Convert invalid PRs to draft automatically (#50467)
kou commentedon Jul 14, 2026
Issue resolved by pull request 50467
#50467