Add PR template.

.github/pull_request_template.md

@@ -0,0 +1,43 @@
+Related Issues: <!-- Add related issues here, e.g. #121 #341 -->
+Requested Reviewers: @andrewtarzia <!-- Add other reviewers here -->
+*Note for Reviewers: If you accept the review request add a :+1: to this post*
+
+<!--
+Talk about what a user would see (a big, a new feature) and what
+user goals weren't being met. If the commit fixes a bug, describe how
+the bug was discovered and steps to reproduce it, unless this is
+already covered by the related issues. If this is a bug fix, what was
+the mistake in the application logic? Be precise. Act like a detective
+and report your findings.
+-->
+
+<!--
+Why did you make the change this way? What other ways did you consider
+but reject? Explain how amazing your work is.
+-->
+
+<!--
+What risks are associated with making the changes in the commit? Will
+anything else break? Are the changes backwards-compatible? Is there
+any "tech debt"?
+-->
+
+<!--
+Explain the source code changes. Changes that are fully explained in
+code comments or the above paragraphs don't need to be repeated here.
+Use bullet points, e.g.
+
+* `src/dynsight/_internal/lens/lens.py:Lens.get_lens()`: The method
+  parameters were updated because <some reason>. The places where
+  the method was called were also updated.
+-->
+
+<!--
+Give evidence that the commit works. Did you visually inspect any
+changes to molecular structures yourself?
+-->
+
+<!--
+The suggested PR outline is taken from
+https://joshuatauberer.medium.com/write-joyous-git-commit-messages-2f98891114c4
+-->

.github/workflows/publish_release.yaml

@@ -20,4 +20,4 @@ jobs:
           twine upload
           -u __token__
           -p ${{ secrets.PYPI_API_TOKEN }}
-          dist/*
+          dist/*