Template Updated

Author: UtkarshMishra-Microsoft

.github/pull_request_template.md

@@ -1,25 +1,40 @@
-### Motivation and Context
-
-<!-- Thank you for your contribution to this repo!
-Please help reviewers and future users, providing the following information:
-  1. Why is this change required? 
-  2. What problem does it solve?
-  3. What scenario does it contribute to?
-  4. If it fixes an open issue, please link to the issue here.
-  5. Does this solve an issue or add a feature that *all* users of this sample app can benefit from? Contributions will only be accepted that apply across all users of this app.
--->
+## Purpose
+<!-- Describe the intention of the changes being proposed. What problem does it solve or functionality does it add? -->
+* ...
 
-### Description
+## Does this introduce a breaking change?
+<!-- Mark one with an "x". -->
 
-<!-- Describe your changes, the overall approach, the underlying design.
-     These notes will help understanding how your code works. Thanks! -->
+- [ ] Yes
+- [ ] No
 
+<!-- Please prefix your PR title with one of the following:
+  * `feat`: A new feature
+  * `fix`: A bug fix
+  * `docs`: Documentation only changes
+  * `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+  * `refactor`: A code change that neither fixes a bug nor adds a feature
+  * `perf`: A code change that improves performance
+  * `test`: Adding missing tests or correcting existing tests
+  * `build`: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
+  * `ci`: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
+  * `chore`: Other changes that don't modify src or test files
+  * `revert`: Reverts a previous commit
+  * !: A breaking change is indicated with a `!` after the listed prefixes above, e.g. `feat!`, `fix!`, `refactor!`, etc.
+-->
 
-### Contribution Checklist
+## Golden Path Validation
+- [ ] I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.
 
-<!-- Before submitting this PR, please make sure: -->
+## Deployment Validation
+- [ ] I have validated the deployment process successfully and all services are running as expected with this change.
 
+## What to Check
+Verify that the following are valid
 - [ ] I have built and tested the code locally and in a deployed app
 - [ ] For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
 - [ ] This is a change for all users of this app. No code or asset is specific to my use case or my organization.
-- [ ] I didn't break any existing functionality :smile:
+
+
+## Other Information
+<!-- Add any other helpful information that may be needed here.. -->