Skip to content

Commit ef89264

Browse files
zaniebhugovkMariatta
authored
Document AI policy labels and when to use them (#1933)
* Document AI policy labels and when to use them * Capitalize "AI" Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> * Use the new AI policy label names The labels were renamed to AI-needs-explanation and AI-guidelines-not-met, matching the names bedevere now acts on. --------- Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Co-authored-by: mariatta <mariatta.wijaya@gmail.com>
1 parent da26e03 commit ef89264

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

‎triage/labels.rst‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -116,6 +116,14 @@ for a list of active branches.
116116
Other labels
117117
============
118118

119+
* Use :gh-label:`AI-guidelines-not-met` for a clearly low-effort
120+
AI-assisted submission where you think the author is unlikely to engage with
121+
feedback. The bot links to the :ref:`guidelines for using AI tools
122+
<ai-tools>` and closes the issue or PR. See the :ref:`triage team's guidance
123+
on closing PRs <triage-team>`.
124+
* Use :gh-label:`AI-needs-explanation` when you have concerns
125+
about AI-assisted work and think the author is likely to engage with feedback.
126+
The bot posts a reminder and leaves the issue or PR open.
119127
* :gh-label:`build`/:gh-label:`performance`: for issues related
120128
to the build process or performance, respectively.
121129
* :gh-label:`easy`: for issues that are considered easy.

0 commit comments

Comments
 (0)