MINOR: [Dev] Ask for generative AI disclosure in PR template - #51282
MINOR: [Dev] Ask for generative AI disclosure in PR template#51282pitrou wants to merge 2 commits into
Conversation
|
How about adding a checkbox instead? (This was partially generated, idea was mine)
Reviewed by:
|
|
I like the checkboxes, yeah! |
|
I would expect that sometimes even the PR description is written by AI. We can tell the submitters to respect the PR template if not properly written. |
kou
left a comment
There was a problem hiding this comment.
+1
I want to keep the "AI generation guidelines" link even if we use the suggested checkbox style.
We can tell the submitters to respect the PR template if not properly written.
It's out of scope of this PR but I want to automate it like our GH-XXX PR title check.
|
|
||
| * [New Contributor's Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request) | ||
| * [Contributing Overview](https://arrow.apache.org/docs/dev/developers/overview.html) | ||
| * [AI-generated Code Guidance](https://arrow.apache.org/docs/dev/developers/overview.html#ai-generated-code) |
There was a problem hiding this comment.
Do we need to delete this line? The guidance link is also provided in Was AI used for this PR? session.
There was a problem hiding this comment.
Do we need to delete this line? The guidance link is also provided in
Was AI used for this PR?session.
No preference from me. @kou What is your opinion?
a64c5c2 to
812b6e5
Compare
812b6e5 to
b327fe6
Compare
I suppose you gained a lot of productivity by generating this. Since multiple boxes can be checked in a list, I removed the superfluous "Human + AI" choices. |
|
To all reviewers: feel free to comment on the updated version! |
|
Looking at #51329 - should we expand this to issue templates? |
Rationale for this change
Often, PR submitters who evidently used AI don't disclose their usage of AI. This adds a nudge to the PR template that they should be upfront about their usage of AI.
The downside is that it's one more question to answer when submitting a PR.
Are these changes tested?
No.
Are there any user-facing changes?
No.