Repository navigation
Document AI policy labels and when to use them - #1933
Conversation
Documentation build overview
|
StanFromIreland
left a comment
StanFromIreland
left a comment
There was a problem hiding this comment.
Will merge once they land.
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
| Other labels | ||
| ============ | ||
|
|
||
| * Use :gh-label:`AI policy close <AI%20policy%20close>` for a clearly low-effort |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
| 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 |
There was a problem hiding this comment.
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?
The labels were renamed to AI-needs-explanation and AI-guidelines-not-met, matching the names bedevere now acts on.
|
I pushed a new commit here, to reflect the actual |
See python/bedevere#722