Skip to content

Add AI tooling info to pull request template #10850

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
westonruter wants to merge 1 commit into
base: trunk
Choose a base branch
from
+7 −0
Open

Add AI tooling info to pull request template #10850

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .github/pull_request_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,18 @@ If this is your first time contributing, you may also find reviewing these guide
- Inline Documentation Standards: https://make.wordpress.org/core/handbook/best-practices/inline-documentation-standards/
- Browser Support Policies: https://make.wordpress.org/core/handbook/best-practices/browser-support/
- Proper spelling and grammar related best practices: https://make.wordpress.org/core/handbook/best-practices/spelling/
- ✨ If you are using AI tools, you must adhere to the AI Guidelines: https://make.wordpress.org/ai/handbook/ai-guidelines/
-->

<!-- Insert a description of your changes here -->

Trac ticket: <!-- insert a link to the WordPress Trac ticket here -->

## Use of AI Tools

<!--
You are free to use artificial intelligence (AI) tooling to contribute, but you must you disclose what tooling you are using and to what extent a pull request has been authored by AI. It is your responsibility to review and take responsibility for what AI generates. See the WordPress AI Guidelines: <https://make.wordpress.org/ai/handbook/ai-guidelines/>.
-->

Comment on lines +23 to +27
Copy link

@justlevine justlevine Feb 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very much spit-balling and not married to any particular phrasing, just trying to list a plurality of acceptable usage as concisely as I can think to.

Suggested change
<!--
You are free to use artificial intelligence (AI) tooling to contribute, but you must you disclose what tooling you are using and to what extent a pull request has been authored by AI. It is your responsibility to review and take responsibility for what AI generates. See the WordPress AI Guidelines: <https://make.wordpress.org/ai/handbook/ai-guidelines/>.
-->
<!--
You may AI tooling to contribute, but it is your responsibly to review, understand, and take ownership of everything the LLM generates. You MUST disclose what tooling was used and where it was used.
For example, please specify if IDE Autocompletions used for code or docs; whether an agent or code harness provided the spec, created some methods or even the initial draft PR, backfilled tests, or generated any non-code assets; etc. See the WordPress AI Guidelines: <https://make.wordpress.org/ai/handbook/ai-guidelines/>.
-->

Copy link
Member Author

@westonruter westonruter Feb 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is enumerating all of the acceptable usage needed? Wouldn't that be better to leave for the contributor to read from the AI Guidelines as they evolve?

Copy link

@justlevine justlevine Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So that's my argument is that it's precisely because AI Guidelines (both ours and general best practices) still have some evolution to do that we need some sort of tangible direction to make it clear we don't need -or want- a play-by-play, but rather something that indicates the signal-to-noise ratio for reviewers.

And to be clear, that's nowhere a full enumeration of acceptable usage, but I do think the rest of what matters can be mostly inferred from those while remaining relatively evergreen ;-) . It's a lot easier to broadly/blindly chunk with a checklist, so I'm doing my best with the constraint and I'm happy to dedupe any you feel are redundant.

Copy link
Member

@mukeshpanchal27 mukeshpanchal27 Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be You may use AI tooling to contribute. Missing use

---
**This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See [GitHub Pull Requests for Code Review](https://make.wordpress.org/core/handbook/contribute/git/github-pull-requests-for-code-review/) in the Core Handbook for more details.**