doc : add pull request template

[purohitdheeraj]

Description

Summary: this PR introduces pull request template file

Fixes #58

Type of change

• 📝 Documentation Update

Added tests?

• 🙅 no, because they aren't needed

would request @nmn for feedback , will update acc

[nmn]

Looks good to me.

@necolas Thoughts on this?

[kevintyj]

I personally prefer a more objective oriented and cleaner PR templates like this:

## What changed / motivation ?

## Linked PR/Issues

## Additional Context
<!--- Screenshots, Tests, Breaking Change, Anything Else ? --->

Then either have a preflight checklist or pre-merge checklist like so:

## Pre-flight checklist 
- [ ] I have read the contributing guidelines [LINK GOES HERE](url)
- [ ] I have signed the contributing agreements
- [ ] I have written unit tests where necessary (If it is a feature commit)
- [ ] Performed a self-review of my code
- [ ] More can come here depending on the details of the contributing guidelines...

---

The sample for this PR would look something like:

What changed / motivation ?

Adds a PR template for new PRs, adds consistency for contributors

Linked PR/Issues

#58

Additional Context

None

Pre-flight checklist

• I have read the contributing guidelines LINK GOES HERE
• I have signed the contributing agreements
• I have written unit tests where necessary (If it is a feature commit)
• Performed a self-review of my code
• Made sure PR title follows the conventional commit specification

---

More info:
The title should hold the information about Type of change this PR is like so:
docs: Add PR template
Also linters for the PR title can be used (like commitlint) to enforce these rules using GitHub Actions.
Having a pre-flight checklist just be a simple checklist allows maintainers to quickly identify if checklists are met quickly in the PR list.

[purohitdheeraj]

thanks @kevintyj for detailed feedback
and yes your PR looks clean and on point , going with that 🚀

[necolas]

@nmn I haven't used PR templates before. I guess I'm a little concerned that having to jump through a lot of hoops makes submitting PRs more tedious, especially for repeat contributors. I don't know that templates make PRs any better

[purohitdheeraj]

Hi @necolas, I agree with you. We could opt for a simpler structure, like in other repos. I think having a PR template can serve as a helpful reminder for adhering to conventions and standards in case someone unintentionally misses them. What's your take on this? we can just keep the most imp stuff there

[nmn]

I share the concerns expressed by @necolas as well. I don't want to put up hurdles to PRs, so I'll leave this PR unmerged for now.

[nestorvanz]

IMO, PR templates should be easy to fill. Let's find a right balance here.

In the other hand, are there any other templates we know are useful?

[purohitdheeraj]

Hi @nmn did the changes and shifted the template file to .github/PULL_REQUEST_TEMPLATE.md from .github/PR_TEMPLATE/pull_request_template.md

[nmn]

Going to merge to try it out for a while. We can revert if we hate it!