Updated PULL_REQUEST_TEMPLATE.md
- [ ] closes #38696
- [ ] tests added / passed
- [ ] passes `pre-commit run --from-ref=upstream/master --to-ref=HEAD --all-files`
- [ ] whatsnew entry


- [ ] closes [#38696](https://github.com/pandas-dev/pandas/issues/38694)
- [ ]  tests added / passed
- [ ]  passes `pre-commit run --from-ref=upstream/master --to-ref=HEAD --all-files`
- [ ] whatsnew entry > Do you want to update this in the template and also in the docs? Feel free to ask if you want/need help with any of this

I would love to contribute 😁 > it's been suggested to **instead** link to the docs and just have "Ensure all linting tests pass, see here how to run them" here

did you mean insert ?
 * [ ]  closes [#38696](https://github.com/pandas-dev/pandas/issues/38694)
* [ ]   tests added / passed
* [ ]   passes `pre-commit run --from-ref=upstream/master --to-ref=HEAD --all-files`
* [ ]  whatsnew entry
* [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) how to run them

Should the new PR include the above details ☝ @MarcoGorelli 
what should be the documentation problem for the new issue mentioned above #### DOC: update contributing.rst                

#### Location of the documentation

doc/source/development/contributing.rst

#### Documentation problem

Need additional information about the command that verifies the linting of code files.

#### Suggested fix for documentation

`pre-commit run --from-ref=upstream/master --to-ref=HEAD --all-files`

The command verifies the linting of code files, it looks for common mistake patterns
*NOTE: An additional paragraph is preferred for this*

☝ Is this issue description appropriate for the new issue? take thanks @BobinMathew  Thankyou @MarcoGorelli and others for the support 🤝