chore(github): sync templates

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

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,3 +1,12 @@
+---
+name: Bug Report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
 <!--- Provide a general summary of the issue in the Title above -->
 # Bug Report 🐛
 <!--- Provide an expanded summary of the issue -->
@@ -31,4 +40,4 @@
 <!--- 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 -->
+<!--- Not obligatory, but suggest an idea for implementing addition or change -->

.github/ISSUE_TEMPLATE/custom-issue.md

@@ -1,3 +1,12 @@
+---
+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 -->
@@ -6,4 +15,4 @@
 <!--- Providing context helps us come to the discussion informed -->
 
 ## Detailed Description
-<!--- Provide any further details -->
+<!--- Provide any further details -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,3 +1,12 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
 <!--- Provide a general summary of the feature in the Title above -->
 # Feature Request 🛍️
 <!--- Provide an expanded summary of the feature -->
@@ -13,4 +22,4 @@
 <!--- 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 -->
+<!--- Provide a detailed description of the change or addition you are proposing -->

.github/pull_request_template.md

@@ -1,14 +1,30 @@
-# Closes #<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`