Skip to content

Document AI policy labels and when to use them #1933

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zanieb wants to merge 2 commits into
base: main
Choose a base branch
from
+8 −0
Open

Document AI policy labels and when to use them #1933

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6edce3e
Document AI policy labels and when to use them
zanieb Oct 23, 2026
2061914
Capitalize "AI"
zanieb Oct 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions triage/labels.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,14 @@ for a list of active branches.
Other labels
============

* Use :gh-label:`AI policy close <AI%20policy%20close>` for a clearly low-effort

@Mariatta Mariatta Oct 27, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In python/bedevere#722 (comment) I suggested alternative labels:

ai-needs-explanation instead of AI policy comment
ai-not-acceptable instead of AI policy close

@Mariatta Mariatta Oct 27, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also mention these labels in the AI policy doc itself to explain how we will react and enforce to AI-assisted contributions. Additionally, triaging doc could benefit from this additional checklist.

AI-assisted submission where you think the author is unlikely to engage with
feedback. The bot links to the :ref:`guidelines for using AI tools
<ai-tools>` and closes the issue or PR. See the :ref:`triage team's guidance
on closing PRs <triage-team>`.
* Use :gh-label:`AI policy comment <AI%20policy%20comment>` when you have concerns

@Mariatta Mariatta Oct 27, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest giving a timeframe that if they aren't responsive after some time, then it should be closed.

Will we then remove the need explanation label and add the not acceptable label? So only one of the two labels can exist?

about AI-assisted work and think the author is likely to engage with feedback.
The bot posts a reminder and leaves the issue or PR open.
* :gh-label:`build`/:gh-label:`performance`: for issues related
to the build process or performance, respectively.
* :gh-label:`easy`: for issues that are considered easy.
Expand Down
Loading