Updating Pull request template. (#304)

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,14 +1,17 @@
 ## Related Tickets
 
+Fixes #ISSUE_NUMBER
+
 <!--
-Please use this format link issue numbers: Fixes #123 / Closes #123
-https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword
+Use this format to link issue numbers: Fixes #123 / Closes #123
+Reference: https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue-using-a-keyword
 -->
 
 ## Description
 
 <!--
-This PR [adds/removes/fixes/replaces] the [feature/bug/etc].
+Briefly explain what this PR does.
+Example: This PR [adds/removes/fixes/replaces] the [feature/bug/etc].
 -->
 
 ## Unexpected difficulties
@@ -24,6 +27,16 @@ Tell us about it, and what you did to overcome them!
 Make sure you test your work before opening a PR.
 Include the precise steps to reproduce in order to peer review your work.
 Also include screenshots if you can so that reviewers can compare with a baseline.
+
+Here is a small list of things you can do to check everything is working:
+ Install Dependencies:- `pnpm install`
+ Build Project:- `pnpm build`
+ Serving To Web:- `pnpm serve`
+ Run Tests:- `npm run test` or `pnpm run test`
+ Check Formatting:- `npm run format` or `pnpm run format`
+ Eslint Check:- `npm run lint:check` or `pnpm run lint:check`
+
+Did you document your code?
 -->
 
 ## Follow-up