Add PR and issue templates

.github/CONTRIBUTING.md

@@ -0,0 +1,14 @@
+### Create Bug Reports
+
+If you find a bug, let us know by creating a new issue.
+
+### Write and submit a patch
+
+If you'd like to fix a bug, you can submit a Pull Request. If possible, raise an issue first and link the issue in your [commit message](https://help.github.com/articles/closing-issues-via-commit-messages/) or [PR's body](https://github.com/blog/1506-closing-issues-via-pull-requests).
+
+When creating Pull Requests, remember:
+
+- [Check In Early, Check In Often](http://blog.codinghorror.com/check-in-early-check-in-often/).
+- Write [good commit messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+- Respect the [Best practices for WordPress development](http://jetpack.com/contribute/#practices).
+

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,40 @@
+---
+name: "Bug report"
+about: Report a bug if something isn't working as expected in WooCommerce PayPal Payments
+
+---
+
+### Describe the bug
+<!-- A clear and concise description of what the bug is. Please be as descriptive as possible; issues lacking detail, or for any other reason than to report a bug, may be closed without action.-->
+
+### To reproduce
+<!-- Describe the steps to reproduce the behavior -->
+1.
+1.
+1.
+
+**Screenshots**
+<!-- If applicable, add screenshots to help explain your problem.-->
+
+### Expected behavior
+<!-- A clear and concise description of what you expected to happen.-->
+
+
+
+**Environment (please complete the following information):**
+ - WordPress Version
+ - WooCommerce Version
+ - WooCommerce PayPal Payments Plugin Version
+ - Browser [e.g. chrome, safari] and Version
+ - Any other plugins installed
+
+### Additional details
+<!--Here you can include any additional details you think might be helpful.-->
+<!--Ticket numbers/links, plugin versions, system statuses etc.-->
+<details><summary>System status</summary>
+
+  ```
+  <!--If applicable, paste the system status here. Please ensure you redact or remove any identifying information. -->
+  ```
+</details>
+

.github/pull_request_template.md

@@ -0,0 +1,26 @@
+<!-- Reference the source of this Pull Request. -->
+<!-- Remove any which are not applicable. -->
+**Issue**: #
+
+---
+
+### Description
+<!-- Describe the changes made in this Pull Request and the reason for these changes. -->
+
+### Steps to test:
+<!-- Describe the steps to replicate the issue and confirm the fix -->
+<!-- Try to include as many details as possible. -->
+1.
+1.
+1.
+
+### Documentation
+<!-- Will this change require new documentation or changes to existing documentation? -->
+<!-- A good way to answer it is to ask: will more than one customer ever need to know about this? -->
+- [ ] This PR needs documentation (has the "Documentation" label).
+<!-- For an extra 💯 include further details about which change requires documentation -->
+
+### Changelog entry
+> Enter a summary of all changes on this Pull Request. This will appear in the changelog if accepted.
+
+Closes # .