Merge pull request #23 from coinbase/coinbase/chore/update-github-tem…

…plates

[chore] updated github templates for issues and pull requests.

.github/ISSUE_REQUEST_TEMPLATE/issue_request_template.md

@@ -0,0 +1,36 @@
+<!---
+ISSUE TITLE: Please make your title easy to understand short summary, usually 4-10 words. Examples:
+
+> Cannot install dependencies due to version error.
+> How do I set a callback redirect url?
+> Curl with API Key not working.
+--->
+
+**Severity:** <severity>
+
+<!---
+Replace <severity> with a priority ranking P0-P3:
+
+> P0: severe/ blocking - completely broken or unusable.
+> P1: high priority - breaking but non-essential.
+> P2: medium priority - non-breaking issue.
+> P3: low priority - questions or nice-to-haves.
+--->
+
+**Description:**
+<description>
+
+<!---
+Replace <description> with a detailed summary of the issue or question, including any relevant context to avoid follow-up questions.
+--->
+
+**Steps to Reproduce:**
+<steps>
+
+<!---
+Replace <steps> with instructions so others can reproduce.
+--->
+
+**Configuration:**
+
+<!--- List your relevant environment/ server/ dependency versions. Any 3rd party plugin use (ie WooCommerce, etc) and corresponding versions. --->

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,51 @@
+<!---
+PR TITLE: Please name your pull request according to this format: [type] short summary. Examples:
+
+> [bugfix] added callback function to charge example.
+> [feature] enabled refunds event signature.
+> [chore] updated docs with webhooks instructions.
+--->
+
+**Issue:** <link>
+
+<!---
+IMPORTANT: Please do not create a Pull Request without creating an issue first. Replace <link> with the url link to the issue.
+--->
+
+**Type:** <type>
+
+<!---
+Same as in title, replace <type> with one of the following options: bugfix | feature | chore
+
+> bugfix: a change which fixes an issue.
+> feature: a change which adds functionality.
+> chore: doc updates, dependencies, refactor, etc.
+--->
+
+**Description:** <description>
+
+<!---
+Replace <description> with a detailed summary of the change, including any relevant context to avoid follow-up questions.
+--->
+
+**Testing:** <testing>
+
+<!---
+Replace <testing> with a description of how you've tested/ verified your changes.
+--->
+
+**Configuration:**
+
+<!---
+List your relevant environment/ server/ dependency versions. Any 3rd party plugin use (ie WooCommerce, etc) and corresponding versions.
+--->
+
+<!---
+CHECKLIST: Please ensure you have done the following.
+> 1. I have performed a self-review of my own code.
+> 2. I have commented my code, particularly in hard-to-understand areas.
+> 3. I have made relevant changes to the documentation.
+> 4. My changes generate no new warnings.
+> 5. I have added any tests that prove my fix is effective or that my feature works.
+> 6. New and existing unit tests pass locally with my changes.
+--->