From eca78074c95ac034c068c0a50f493ca86cb33d06 Mon Sep 17 00:00:00 2001
From: Brian Degenhardt <bmd@bmdhacks.com>
Date: Fri, 7 Aug 2026 14:26:52 -0700
Subject: [PATCH] GitHub: soften the AI-assistance question in the PR template

The template was inherited from PCSX2, where the AI section is a yes/no
question a contributor must answer and a link to upstream's LLM usage
policy. That policy is not ours to enforce, and the framing treats
AI-assisted work as something to be declared rather than reviewed.

Replace it with an optional note. The requirements that actually matter
apply to every PR regardless of how it was written: the author
understands the change, can explain why it is correct, and has built and
tested it.
---
 .github/PULL_REQUEST_TEMPLATE.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 94f106dcf1..d6b66496f7 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -7,5 +7,5 @@
 ### Suggested Testing Steps
 <!-- If applicable, including examples you've already tested with / recommendations for how to test further is very helpful! -->
 
-### Did you use AI to help find, test, or implement this issue or feature?
-<!-- Answer yes or no. If you answer yes, please provide a brief explanation as to how you used it. Please see the Large Language Model (LLM) Usage Policy for more information: https://pcsx2.net/docs/contributing/#large-language-model-llm-usage-policy -->
\ No newline at end of file
+### AI Assistance (optional)
+<!-- AI-assisted contributions are welcome here — we use these tools ourselves, and this is not a gate on your PR. If AI did a meaningful share of the work, a line on where it helped lets reviewers focus their attention. What we ask regardless of how the patch was written: you understand the change, you can explain why it is correct, and you have built and tested it. We review the code, not the toolchain. -->
\ No newline at end of file