MAINT: add AI disclosure to pr template#31124
Conversation
|
Is this instead of #31043, or in addition? |
In addition - we want all contributors to disclose AI and we want to reassure new contributors it's so we can give 'em good feedback (which is why I didn't put it here) Probably should have just added to that PR but was thinking of them as separate discussions/tasks. |
story645
force-pushed
the
pr-template
branch
4 times, most recently
from
f62c7d6 to
585373d
Compare
rcomer
left a comment
rcomer
left a comment
There was a problem hiding this comment.
Does this count as docs, or do we need two approvals?
🤷♀️ I'm fine w/ more than one as it's kinda an implicit policy change. |
timhoffm
left a comment
timhoffm
left a comment
There was a problem hiding this comment.
Good as a starting point. It's still a bit vauge:
-
"used AI in writing this PR": Does this mean the code or the PR description or both? Do we need to be more explicit?
-
"please describe how" also leaves room for interpretation and may be difficult to answer for someone who is serious about it. Likely we only want to know "for getting ideas" / "for writing the code" / "for rewording the PR message" / "I promted AI to solve the problem" / "I told an agent to find and fix FOSS issues". But one could answer much more detailed.
As a minimal improvement maybe "please briefly describe" how.
Overall, I think we need to gradually improve on the topic.
it's purposely broad - I wanna see what responses we get before fine tuning, and also we do care about both.
Again trying to leave space for openness - we'd rather someone tell us about AI use we don't care about (research) than not tell us about AI we do. |
story645
force-pushed
the
pr-template
branch
from
585373d to
5ca3290
Compare
story645
force-pushed
the
pr-template
branch
from
5ca3290 to
a710e4a
Compare
github-actions
bot
added
Documentation: devdocs
|
@rcomer added your wording from #30848 (comment) to the second commit |
story645
force-pushed
the
pr-template
branch
from
b990b8f to
856e477
Compare
|
Failing tests unrelated, moved notes about translation to #31163 |
story645
force-pushed
the
pr-template
branch
from
856e477 to
6273092
Compare
|
Let's take this. We can always refine later. |
4 participants
PR summary
Jumping off the discussion in #30848 and my wanting to add a disclosure to a PR to model the behavior I want to see, added a section on AI disclosure cause that seemed the easiest. Going simple here in the spirit of #30848 (comment) and we can always add more later.
PR checklist