chore: updated pull request template

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,4 +1,39 @@
-Pull-Request
+<!--
+
+Some key notes before you open a PR:
+
+ 1. Select which branch should this PR be merged in?
+ 2. PR name follows [convention](http://karma-runner.github.io/4.0/dev/git-commit-msg.html)
+ 3. Update necessary Documentation
+ 4. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes
+
+
+Also, if you're new here
+
+- Documentation Guidelines => https://github.com/frappe/erpnext/wiki/Updating-Documentation
+
+- Contribution Guide => https://github.com/frappe/bench/blob/master/docs/contribution_guidelines.md
+
+- Pull Request Checklist => https://github.com/frappe/erpnext/wiki/Pull-Request-Checklist
+
+-->
+
+What type of a PR is this?
+
+- [ ] Changes to Existing Features
+- [ ] New Feature Submissions
+- [ ] Bug Fix
+- [ ] Breaking Change (include change in API behaviours, etc.)
+
+---
+
+> Please provide enough information so that others can review your pull request:
+
+<!-- You can skip this if you're fixing a typo or updating existing documentation -->
+
+---
+
+> Explain the **details** for making this change. What existing problem does the pull request solve? The following checklist could help
 
 - [ ] Have you followed the guidelines in our Contributing document?
 - [ ] Have you checked to ensure there aren't other open [Pull Requests](../pulls) for the same update/change?
@@ -11,18 +46,8 @@ Pull-Request
 
 ---
 
-What type of a PR is this? 
+<!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. -->
 
-- [ ] Changes to Existing Features
-- [ ] New Feature Submissions
-- [ ] Bug Fix
-- [ ] Breaking Change
-
---- 
-
-- Motivation and Context (What existing problem does the pull request solve):
-- Related Issue: 
-- Screenshots (if applicable, remember, a picture tells a thousand words): 
-
-**Please don't be intimidated by the long list of options you've fill. Try to fill out as much as you can. Remember, the more the information the easier it is for us to test and get your pull request merged** :grin: 
+> Screenshots/GIFs
 
+<!-- Add images/recordings to better visualize the change: expected/current behviour -->