From 5b44d9937532404840c2134c357d7697a0e95984 Mon Sep 17 00:00:00 2001
From: Ken Simon <ksimon@nvidia.com>
Date: Mon, 13 Jul 2026 10:48:47 -0400
Subject: [PATCH] PR template: Add guidance on a good PR description

---
 .github/PULL_REQUEST_TEMPLATE.md | 21 ++++++++++++++++++---
 1 file changed, 18 insertions(+), 3 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 6350e3c9ab..537c1e685e 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,4 +1,15 @@
-<!-- Describe what this PR does -->
+<!--
+Description: Describe what this PR does, focusing on *why* you are making this
+change. What problem is it solving? What motivated making this change? Assume
+the audience has no other context: Don't assume people are already aware of
+your feature roadmap. If a linked GitHub issue contains the necessary context,
+repeat enough of it here to help people understand it at a glance, then link to
+it below. PR descriptions are not just for code review, they're also for
+helping people understand why a given change happened after it merges. Please
+keep both audiences in mind for your PR description.
+
+NOTE: Delete all commented sections like this one before submitting your PR.
+-->
 
 ## Related issues
 <!-- Refer to existing GitHub issues here -->
@@ -12,8 +23,12 @@
 - [ ] **Internal** - Internal changes (refactoring, tests, docs, etc.)
 
 ## Breaking Changes
-<!-- If checked, describe the breaking changes and migration steps -->
-<!-- Breaking changes are not generally permitted, please discuss on a GitHub discussion or with the development team if you believe you need to break a backward compatibility guarantee -->
+<!--
+If checked, describe the breaking changes and migration steps. Breaking changes
+are not generally permitted, please discuss on a GitHub discussion or with the
+development team if you believe you need to break a backward compatibility
+guarantee
+-->
 - [ ] **This PR contains breaking changes**
 
 ## Testing