chore(github): sync templates

Signed-off-by: irmerk <jolenelanglinais@gmail.com>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,38 +1,43 @@
 ---
-name: Bug report
+name: Bug Report
 about: Create a report to help us improve
 title: ''
 labels: ''
 assignees: ''
 
 ---
 
-**Describe the bug**
-A clear and concise description of what the bug is.
+<!--- Provide a general summary of the issue in the Title above -->
+# Bug Report 🐛
+<!--- Provide an expanded summary of the issue -->
 
-**To Reproduce**
-Steps to reproduce the behavior:
-1. Go to '...'
-2. Click on '....'
-3. Scroll down to '....'
-4. See error
+## Expected Behavior
+<!--- Tell us what should happen -->
 
-**Expected behavior**
-A clear and concise description of what you expected to happen.
+## Current Behavior
+<!--- Tell us what happens instead of the expected behavior -->
 
-**Screenshots**
-If applicable, add screenshots to help explain your problem.
+## Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
 
-**Desktop (please complete the following information):**
- - OS: [e.g. iOS]
- - Browser [e.g. chrome, safari]
- - Version [e.g. 22]
+## Steps to Reproduce
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
 
-**Smartphone (please complete the following information):**
- - Device: [e.g. iPhone6]
- - OS: [e.g. iOS8.1]
- - Browser [e.g. stock browser, safari]
- - Version [e.g. 22]
+## Context (Environment)
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+### Desktop
+ - OS: [e.g. macOS]
+ - Browser: [e.g. Chrome, Safari]
+ - Version: [e.g. 0.22.15]
 
-**Additional context**
-Add any other context about the problem here.
+## Detailed Description
+<!--- Provide a detailed description of the change or addition you are proposing -->
+
+## Possible Implementation
+<!--- Not obligatory, but suggest an idea for implementing addition or change -->

.github/ISSUE_TEMPLATE/custom-issue.md

@@ -1,10 +1,18 @@
 ---
-name: Custom issue
-about: Describe this issue's purpose here.
+name: Custom Issue
+about: For miscellaneous, such as questions, discussions, etc.
 title: ''
 labels: ''
 assignees: ''
 
 ---
 
+<!--- Provide a general summary of the issue in the Title above -->
+# Discussion 🗣
+<!--- Provide an expanded summary of the issue -->
 
+## Context
+<!--- Providing context helps us come to the discussion informed -->
+
+## Detailed Description
+<!--- Provide any further details -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +1,25 @@
 ---
-name: Feature request
+name: Feature Request
 about: Suggest an idea for this project
 title: ''
 labels: ''
 assignees: ''
 
 ---
 
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+<!--- Provide a general summary of the feature in the Title above -->
+# Feature Request 🛍️
+<!--- Provide an expanded summary of the feature -->
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+## Use Case
+<!--- Tell us what feature we should support and what should happen -->
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+## Possible Solution
+<!--- Not obligatory, but suggest an implementation -->
 
-**Additional context**
-Add any other context or screenshots about the feature request here.
+## Context
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Detailed Description
+<!--- Provide a detailed description of the change or addition you are proposing -->

.github/pull_request_template.md

@@ -1,14 +1,30 @@
-# Issue #<NUMBER HERE>
-<OVERALL SUMMARY OF PULL REQUEST>
+<!--- Provide a formatted commit message describing this PR in the Title above -->
+<!--- See our DEVELOPERS guide below: -->
+<!--- https://github.com/accordproject/techdocs/blob/master/DEVELOPERS.md#commit-message-format -->
+# Closes #<CORRESPONDING ISSUE NUMBER>
+<!--- Provide an overall summary of the pull request -->
 
 ### Changes
-- <INSERT DESCRIPTION OF CHANGES>
-  - <SUB NOTES OF DESCRIPTIONS>
-- <SUMMARIZE ALL COMMITS IN PULL REQUEST>
+<!--- More detailed and granular description of changes -->
+<!--- These should likely be gathered from commit message summaries -->
+- <ONE>
+- <TWO>
 
 ### Flags
-- <DESCRIBE ISSUES OR HOLDS FOR REVIEWERS>
+<!--- Provide context or concerns a reviewer should be aware of -->
+- <ONE>
+- <TWO>
+
+### Screenshots or Video
+<!--- Provide an easily accessible demonstration of the changes, if applicable -->
 
 ### Related Issues
-- Issue #<NUMBER HERE>
-- Pull Request #<NUMBER HERE>
+- Issue #<NUMBER>
+- Pull Request #<NUMBER>
+
+### Author Checklist
+- [ ] Ensure you provide a [DCO sign-off](https://github.com/probot/dco#how-it-works) for your commits using the `--signoff` option of git commit.
+- [ ] Vital features and changes captured in unit and/or integration tests
+- [ ] Commits messages follow [AP format](https://github.com/accordproject/techdocs/blob/master/DEVELOPERS.md#commit-message-format)
+- [ ] Extend the documentation, if necessary
+- [ ] Merging to `master` from `fork:branchname`