From 526f168120be7a7ea9de6e0585baddb8872ef318 Mon Sep 17 00:00:00 2001
From: Oleksandr Ivantsiv <oivantsiv@nvidia.com>
Date: Fri, 8 May 2026 23:34:12 +0000
Subject: [PATCH] Add PR template and align copilot-instructions

Add a pull_request_template.md with the standard SONiC PR sections
(What I did / Why I did it / How I verified it / Details if related)
and align the PR description guidance in copilot-instructions.md to
reference the same sections.

Signed-off-by: Oleksandr Ivantsiv <oivantsiv@nvidia.com>
---
 .github/copilot-instructions.md  |  6 ++++++
 .github/pull_request_template.md | 19 +++++++++++++++++++
 2 files changed, 25 insertions(+)
 create mode 100644 .github/pull_request_template.md

diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
index 2295e1ca9..e57d2a2c9 100644
--- a/.github/copilot-instructions.md
+++ b/.github/copilot-instructions.md
@@ -76,6 +76,12 @@ Kernel patches are accepted under these conditions:
 - **Upstream first**: Prefer upstream patches — include the original commit hash
 - **Justification**: Explain why a patch is needed and why it can't be done out-of-tree
 - **CI**: Azure pipeline checks must pass
+- **PR description template**: Fill out all sections of the [PR template](pull_request_template.md) when submitting a pull request:
+  - **What I did**: Summarize the change being made
+  - **Why I did it**: Explain motivation and context for the change
+  - **How I verified it**: Provide steps or commands to test the change
+  - **Details if related**: Include any additional context, links, or related information
+
 
 ## Gotchas
 
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 000000000..05366e3ff
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,19 @@
+<!--
+Please make sure you have read and understood the contribution guildlines:
+https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md
+
+1. Make sure your commit includes a signature generted with `git commit -s`
+2. Make sure your commit title follows the correct format: [component]: description
+3. Make sure your commit message contains enough details about the change and related tests
+4. Make sure your pull request adds related reviewers, asignees, labels
+
+Please also provide the following information in this pull request:
+-->
+
+**What I did**
+
+**Why I did it**
+
+**How I verified it**
+
+**Details if related**