AI Guidelines should be referenced in the pull request template

[westonruter]

New ​WordPress AI Guidelines have been published. See ​announcement. These should be referenced in the ​pull request template since a lot of new PRs are being opened with the assistance of AI tooling.

For reference, the WordPress/performance repo's ​pull request template currently includes this AI guidance.

Trac ticket: https://core.trac.wordpress.org/ticket/64587

This incorporates aspects of the ​PR template from the WordPress/performance repo, namely the new “Use of AI Tools” section.

I'm not familiar with the conversation and Chesterton fences that went into WordPress/performance, but as I outline in ​https://github.com/WordPress/ai/issues/77, I'd a recommend a checklist (or commented list if we care about GitHub UI semantics) versus a "free text" section.

IMO much better DX choice than expecting contributors - even if/after reading the guidelines- to intuitively know and remember what they need to proactively disclose / how granularly to go, etc. Also has the added benefit of guiding users to potential constructive uses of AI without being overbearing.

@justlevine I think that's a good suggestion, but I'm wary of adding too much to the template since it is currently pretty streamlined. Maybe start with simple freeform and links to the (in progress) guidelines and then iterate once the guidelines are more mature? Maybe the guidelines could have such a list of bullet points incorporated into it for copying into the PR template. It could even have an example PR template as part of the guidelines. My primary concern is to get something out the door sooner than later to help address the influx of PRs, many of which appear to be authored with in AI.

@westonruter yup agree 100%, especially the part that something here is better than nothing.

Maybe the guidelines could have such a list of bullet points incorporated into it for copying into the PR template. It could even have an example PR template as part of the guidelines.

My hope is to create less cognitive load, so while I love the idea of providing some examples _of_ what disclosure looks like, I think a copy->paste flow from an external ref document isn't worth the friction.

Still, even if it's just 1 extra sentence in the , I do think we should provide at least _some_ same-place signposting. Personally, I feel it's more important to have this while waiting for the guidelines have time percolate, since the whole point is we're asking folks to do something _now_ that's new to contributors, guideline authors, and really the entire ecosystem, before there's anywhere else to provide relatively clear direction.

(Related: Some fun reading at where folks are discussing the issues and potential tools GitHub could offer maintainers to triage slop ​https://github.com/orgs/community/discussions/185387)

Still, even if it's just 1 extra sentence in the , I do think we should provide at least _some_ same-place signposting.

Would you add a suggestion for what you have in mind?

[westonruter]

Related: #63901 (Add AGENTS.md for the project)

Having this context will be very helpful for Copilot (and other agents) to perform accurate suggestions and reviews.

[westonruter]

In 61593:

General: Add AI Guidelines to the pull request template.

Developed in ​https://github.com/WordPress/wordpress-develop/pull/10850

Props westonruter, justlevine, mukesh27, jeffpaul.
See #64587.

I've committed the initial version of this in r61593.

[westonruter]

Even though I've committed the initial version of this in [61593], I'm leaving this open for additional refinement.

[desrosj]

Thanks for adding this, all!

I have one request for a refinement. Could we add an example that shows the information contributors are expected to include and how to ideally format it? And possibly a template that can just be filled in below that.

There is a ​great example in the guidelines. But even when someone is very familiar with the guidelines and expectations, it can be (easy to forget|hard to remember) everything that should be included (as a Core Committer, I drive a good amount of traffic to the ​Commit Messages best practices page).

This would also help to make disclosures more consistent and easier to spot or scan while reviewing PRs.

[desrosj]

I noticed just now that the Gutenberg repository's PR template needs to be updated to include this as well.

[westonruter]

PR for Gutenberg: ​https://github.com/WordPress/gutenberg/pull/76425